What can you explain with Layup?
The examples below are starting points. Each opens with editable source in the playground; downloads include the source so you can keep a diagram in version control.
| Example | What it demonstrates | Edit |
|---|---|---|
| First diagram | Cards, code, automatic tones, typed relationships | Open |
| Service architecture | Boundaries, groups, rows, and component relationships | Open |
| Support decision tree | Diamond questions, outcomes, and subtree lanes | Open |
| Job lifecycle | Initial/final states, cycles, and self-transitions | Open |
| Composite connection states | Nested scopes and cross-boundary transitions | Open |
| Request sequence | Async work, returns, retries, notes, and alternatives | Open |
| CJK and Arabic sequence | Multiline messages and script shaping | Open |
| Right-to-left graph | Independent text and graph directions | Open |
| Slide-sized pipeline | Uniform fitting and readability checks | Open |
| Request/retry presentation | Shared sequence model and four reveal steps | Open |
| Shared architecture views | Overview/detail filtering with stable identities | Open |
For automatically generated diagrams, see generation from analysis. Its canonical JSON example describes this repository's Cargo workspace with an overview and per-package dependency/target views; it uses the APIs and CLI rather than the DSL playground.
Decision: where should a request go?
Sequence: show an asynchronous handoff
State: show a lifecycle
The repository examples contain the canonical fixtures used by the editor, tests, and visual galleries. They describe fictional systems and are intended to teach the diagram language.