Time, composition and linked documentation
Gantt / supplied-date schedule
A schedule from supplied dates: bars per task on a calendar, dependencies as links.
timeline.basic@1New DDN source
Why use it?
Dates are data — a Gantt you can edit in source stays honest when the plan moves.
When it helps
Any dated plan small enough to read on one page.
How to read it
- Bars are declared spans, not estimates the chart invented.
- A dependency arrow is finish-to-start; it constrains reading, not the calendar.
What you need
- The tasks with start/end
- The dependencies
- Today's date for context
Things to check
- Do not schedule a task before its predecessor without a note.
- Do not let the chart silently shift dates — every date is in the source.
Scope of this diagram
Supplied dates only; no scheduling algorithm runs.
Work with the converted example
- Open the viewer and select
gantt. 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.