Techniques
Route options — curved, orthogonal and rounded
Relation routing as a declaration: curved flows, orthogonal corridors, rounded corners — and per-relation overrides.
ddn@1New DDN source
Why use it?
Routing is readability infrastructure: the same graph reads cleanly or not at all depending on the corridors.
When it helps
Dense diagrams, publication-quality output, or matching a house routing style.
How to read it
- Switch variants: same graph, different route geometry — curved for organic flow, orthogonal for engineering reading.
- The mixed variant shows overrides: one view, independent route styles per relation.
What you need
- The model
- The routing declaration per view or per relation
Things to check
- Do not mix route styles without a reason — the mixed variant is a capability demo, not a recommendation.
- A route is never a fact: crossings and curves carry no semantics.
Scope of this diagram
Declared routing options; the router optimises within the declaration, it does not infer intent.
Work with the converted example
- Open the viewer and select
mindmap_classic. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.