Diagrams as Code 2.0
summary
Argues for a model-first approach where a single workspace model and view definitions generate consistent diagrams across formats, not one text file per picture. Uses a domain-specific language called Structurizr DSL, a CLI exporter and a Dockerized web app Structurizr Light, and outputs PlantUML, Mermaid, DOT, and ilograph. Features include inferred higher‑level relationships, theming/CSS-like styling, scripting and plugin hooks, interactive zoomable diagrams, docs/ADR embedding, and successful open‑source tooling that keeps diagrams in sync.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:09C4 Model
- 6:05Diagramming vs modelling
- 7:54Domain concepts
- 8:41Model-based (DRY)
- 12:41HTML & CSS
- 15:44Diagrams as code 1.0
- 16:02Diagrams as code 2.0
- 20:13More advanced features
- 24:04Enterprise-wide modelling?
- 25:09Scripting support
- 26:36Plugin support
- 28:58Custom tooling
- 30:23Usage scenarios
- 31:24Interactive diagrams
- 35:19Closing thoughts
- 38:49Outro
related talks
34mDiagram as Code - Decoding Architectural Diagrams
43mC4 models as code
42mStructurizr DSL: Beyond Diagrams to Architecture-as-Code
50mVisualise, Document & Explore Your Software Architecture
50mDesign Patterns for Software Diagramming
41mDesign Patterns for Software Diagramming
15mC4 Model, the Solution to Standardize My Architecture Diagrams?
49mReverse-engineering Architecture Diagrams