- 4 minutes to read
Technical Reference
This reference describes what users can do with Architecture Diagrams in Nodinite.
It is intentionally focused on available features and supported workflows, not internal implementation details.
Scope of This Reference
Use this page when you need:
- a capability overview of View mode vs Designer mode
- a practical guide to Import/Export options
- a quick map of Web API endpoint families for automation and integration
- lifecycle guidance for Draft and Active diagrams
Capability Matrix - View Mode vs Designer Mode
The matrix below compares what is available in each mode.
Legend:
- Available
- Not available
- Draft only: Requires diagram state = Draft
| Capability | View mode | Designer mode |
|---|---|---|
| Interactive canvas (pan, zoom, fit) | ||
| Node, connector, and boundary inspectors | ||
| Drill-through navigation and linked diagram actions | ||
| Collapse/expand and focus boundaries | ||
| Monitoring overlays and status refresh | ||
| Open Mermaid companion view/modal | ||
| Export diagram artifacts | ||
| Print-focused usage | ||
| Generate runtime Dynamic diagram from log activity | ||
| Edit diagram metadata (properties) | ||
| Sync related diagrams and links | ||
| Create/clone/promote diagram versions | ||
| Toolbox (add new elements) | Draft only | |
| Move and resize elements | Draft only | |
| Create connectors from ports/handles | Draft only | |
| Edit node, connector, and boundary properties | Draft only | |
| Reparent elements across boundaries | Draft only | |
| Delete elements | Draft only | |
| Auto-arrange layout |
Lifecycle Matrix - Draft vs Active
Diagram lifecycle controls editing behavior.
| Lifecycle state | Intended use | Editing behavior | Typical actions |
|---|---|---|---|
| Draft | Authoring and change iteration | Full editing enabled | Add/move/resize elements, update metadata, adjust connectors, run auto-arrange |
| Active | Published reference and operational consumption | Read-only canvas behavior | Navigate, inspect, export, print, monitor, analyze runtime behavior |
Guidance:
- Use Draft while building or revising diagrams.
- Promote to Active when the diagram should be consumed as the trusted reference.
Import Support
Import is intended for bringing existing architecture definitions into a diagram set with preview and conflict handling.
Import workflow
- Validate source content.
- Review inferred matches and unresolved items.
- Apply with conflict resolution choices.
- Open the resulting diagram in View or Designer mode.
Import capabilities
| Capability | Support |
|---|---|
| Validation before apply | |
| Conflict review and resolution | |
| Entity matching and override options | |
| Apply into an existing diagram set | |
| Link synchronization after import |
Export Support
Export supports both visual sharing and source-oriented interchange.
Per-diagram export formats
| Format | Typical use |
|---|---|
Markdown (export.md) |
Source-level review, collaboration, and version diff workflows |
SVG (export.svg) |
High-fidelity vector sharing and documentation embedding |
PNG (export.png) |
Lightweight image sharing and presentations |
Draw.io (export.drawio) |
Interchange with draw.io-based workflows |
PlantUML (export.puml) |
Interchange with PlantUML ecosystems |
Diagram-set export formats
| Format | Typical use |
|---|---|
SVG ZIP (export/svg.zip) |
Batch export of an entire set as vector assets |
PNG ZIP (export/png.zip) |
Batch export of an entire set as raster assets |
Web API Reference (User-Facing Families)
The Architecture Diagram APIs are organized into endpoint families. Use Swagger/OpenAPI in your environment for complete request/response contracts.
Core families
| Endpoint family | Purpose |
|---|---|
/api/C4Diagrams |
Diagram CRUD, lifecycle actions, view-mode data, dynamic generation, export, links, tags, metadata |
/api/C4DiagramSets |
Diagram set CRUD, set-level operations, batch exports |
/api/c4diagrams/import |
Import validation and apply |
/api/C4Diagrams/{diagramId}/nodes/{nodeId}/articles |
Node-to-article linking and candidate discovery |
Common automation scenarios
| Scenario | Typical API path |
|---|---|
| Create and maintain diagrams | C4Diagrams + C4DiagramSets |
| Promote draft to active | C4Diagrams lifecycle endpoints |
| Validate and apply import content | c4diagrams/import/validate and c4diagrams/import/apply |
| Export single diagrams or full sets | C4Diagrams export endpoints and C4DiagramSets ZIP export endpoints |
| Synchronize and maintain cross-diagram links | C4Diagrams link endpoints |
Practical Recommendations
- Use View mode for analysis, sharing, and operations-facing usage.
- Use Designer mode for controlled authoring in Draft state.
- Use Import Validate before Apply to reduce correction cycles.
- Standardize on one export format per audience:
- SVG for technical documentation
- PNG for quick sharing
- Markdown/Draw.io/PlantUML for interchange workflows
- Treat Active diagrams as the canonical reference for stakeholders.