Time, composition and linked documentation
Composed dashboard / report page
Several views composed on one page: charts, tables and a graph sharing one model and one data block.
panels.composed@1New DDN source
Why use it?
The dashboard is the summary stakeholders actually read — and it refreshes as one transaction, not nine.
When it helps
Periodic operations and quality reporting.
How to read it
- Panels are views of the same records — a number that disagrees with its chart is a defect, not a refresh lag.
- Composition is one level deep, by rule.
What you need
- The panels to show
- The shared data block
- The refresh cadence
Things to check
- Do not nest a dashboard in a dashboard.
- Do not add a panel that answers a question nobody asked.
Scope of this diagram
One composition level with per-panel budgets; refresh swaps records atomically.
Work with the converted example
- Open the viewer and select
dashboard_quality. 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.