Techniques
Looks — classic, hand-drawn and neo
The same model rendered in each built-in look: precise single strokes, organic pen strokes, raised precise cards.
ddn@1New DDN source
Why use it?
The look is a view choice, not data — the right reading context (review vs workshop vs deck) picks the look.
When it helps
Choosing a house style, or matching the diagram to the meeting: hand-drawn invites change, classic asserts precision.
How to read it
- Switch variants: the model, layout and labels are identical — only the stroke treatment changes.
- Hand-drawn is deterministic here, not random: the same source always renders the same strokes.
What you need
- The model
- The look declaration on the view
Things to check
- Do not signal "draft" with a hand-drawn look on a baselined model — say the status in words.
- Never compare measurements across looks; strokes differ, data does not.
Scope of this diagram
The three built-in looks; custom strokes are a publication-format concern, not assumed here.
Work with the converted example
- Open the viewer and select
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.