Hierarchies, maps and symbol libraries
Icon pack symbols in a network
A network drawn with the bundled icon packs: devices and services rendered as recognisable symbols instead of boxes.
network.basic@1New DDN source
Why use it?
Ops readers find a router icon faster than a labelled rectangle — recognition beats reading at incident time.
When it helps
Infrastructure diagrams for audiences who know the vendor/icon vocabulary.
How to read it
- Icons are declared per element; the node still carries its label and relations.
- Count from the catalogue: the icon packs ship with the runtime, nothing loads remotely.
What you need
- The elements
- The icon choice per element
- The relations
Things to check
- Do not mix metaphors (cloud icon for an on-prem box) to fill space.
- An icon does not replace the label — exports and search read the label.
Scope of this diagram
Bundled icon packs only (count from facts.json); custom icons are a publication choice, not assumed.
Work with the converted example
- Open the viewer and select
net. 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.