Techniques
Text presentation — readable typography and Markdown
Use registered font and text properties for overall presentation, and supported Markdown inside narrative text for local emphasis.
ddn@1New DDN source
Why use it?
Emphasis that lives only in a viewer's session preview vanishes on export; declared in the model it survives publication, diffing and hand-off to any conformant tool.
When it helps
A label that must read as retired (strike), a display name in small caps, an emphasised (bold/italic) element, a coloured label, or decorated header/footer chrome.
How to read it
- File settings override eligible CSS presentation settings, then standard defaults apply.
- Notes support headings, emphasis, strong emphasis, lists and the DDN underline extension.
- Identifiers and typed data remain plain unless their role explicitly supports formatting.
What you need
- The text owner
- The intended font and supported formatting
- The target output size
Things to check
- Raw HTML is not interpreted as arbitrary page content.
- Do not change an identifier just to obtain a different displayed title.
Scope of this diagram
Formatting follows the supported DDN text profile and the selected role’s property contract.
Work with the converted example
- Open the viewer and select
main. 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.