5 Commits
Author SHA1 Message Date
Stephan BehnkeandGitHub fd9e9adf1b Document CHASM (#9689)
WISOTT

Rendered:
https://github.com/temporalio/temporal/blob/stephanos/chasm-graph/docs/architecture/chasm.md
2026-04-02 22:04:42 +00:00
b435e2f727 Define layout engine in d2 file (#9697)
## What changed?

Moved decision which d2 layout engine to use into file.

## Why?

Allows each file to pick the right layout engine for itself.

Co-authored-by: Hanzo Dev <[email protected]>
2026-03-30 17:08:45 +00:00
Stephan BehnkeandGitHub 02a9896e1a Tweak retry documentation (#5998)
## What changed?
<!-- Describe what has changed in this PR -->

Added a diagram to the retries.md docs.

## Why?
<!-- Tell your future self why have you made these changes -->

To make it clearer what's going on.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2024-05-24 14:25:19 -07:00
Michael SnowdenandGitHub c504991e6d Reorganize docs (#5535)
## What changed?
<!-- Describe what has changed in this PR -->
I reorganized our docs into `docs/{admin,architecture,development}`.

## Why?
<!-- Tell your future self why have you made these changes -->
We discussed this internally, but I believe this is a better
segmentation for the different audiences looking at our docs. I plan on
adding more stuff to docs/admin like metrics and dynamic config docs.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
I'm mainly looking for broken links.
- I went through each markdown file in docs manually. 
- I looked through all inspection errors in the IDE.
- I looked at all references to "docs/" or "develop/" in our code.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2024-03-18 23:13:02 -07:00
fa865b13e0 docs: add PR template reminder, Makefile, and assets folder (#5423)
## What changed?
- Add PR template reminder to update docs
- Add first d2 diagram to Matching README (more to follow)
- Refactor `docs` folder to contain an `assets` folder where we store
images for all the READMEs in the project, instead of using github
assets

## Why?
To improve how we interact with and update docs

## How did you test it?
n/a

## Potential risks
n/a

## Is hotfix candidate?
no

---------

Co-authored-by: Stephan Behnke <[email protected]>
Co-authored-by: Dan Davison <[email protected]>
2024-02-21 11:28:10 -08:00