Hierarchies, maps and symbol libraries
Isometric architecture view
A platform architecture drawn as an isometric block map: tiers as slabs, systems as blocks on them.
ddn@1New DDN source
Why use it?
The iso view reads like a model of the estate — useful when the audience thinks in buildings, not boxes.
When it helps
Poster architecture overviews and onboarding decks.
How to read it
- Slabs are tiers; blocks on a slab are its systems; connectors still carry the declared relations.
- The same model renders flat elsewhere — the geometry is a view choice, not data.
What you need
- The tiers and systems
- The relations between them
Things to check
- Do not let occlusion hide a system — rotate the narrative, not the truth.
- Iso is for orientation; detail reviews belong on the flat view.
Scope of this diagram
An isometric projection of the declared model; placement on slabs is declared, not inferred.
Work with the converted example
- Open the viewer and select
iso_map. 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.