Workspaces
Structure
Map pages, user journeys, and technical architecture together on one canvas.
Structure combines the page map, user journeys, and technical architecture. Place related diagrams near one another, use titles and paragraphs to explain them, and connect nodes where a relationship matters.
Written project context and brand guidance belong in Documentation. Ordered page sections belong in Pages.
Add nodes quickly
Move your pointer to the intended canvas position and press a quick key. You can also use a visible tool button, or press A to open the searchable Add picker. Quick keys are inactive while you are typing in an editor or field.
| Key | Node | Purpose |
|---|---|---|
| 1 | Page | A route, screen, or page template. |
| 2 | Note | Supporting context or an assumption. |
| 3 | Feature / step | A capability or significant step in a journey. |
| 4 | API / integration | An external service or system boundary. |
| 5 | Constraint | A requirement or limitation. |
| 6 | Actor | The person or role completing a journey. |
| 7 | Decision | A meaningful branch or choice. |
| 8 | Service / module | An implementation responsibility or application capability. |
| 9 | Datastore / CMS | A database, content platform, search index, or other store. |
| T | Title | A large heading for an area of the canvas. |
| P | Paragraph | Supporting text with line breaks. |
Data model, Tracking, and Stack are also available in the Add picker. Search by the name or purpose of the node you need.
Map pages and routes
Use a Page node for each meaningful route or screen. Give it a clear title, path, and short description of its purpose. Structure owns the page list and direct hierarchy; those pages are available for composition in Pages.
Connect direct parent and child pages rather than every possible navigation link:
Home
├── About
├── Blog
│ └── Blog Post
└── Contact
A Feature can sit beside the map when a capability is important but is not itself a route. Use a Constraint for restrictions such as authentication, regional availability, or exclusion from navigation.
Map user journeys
Build a focused path around a user's goal:
New customer → Sign up → Select plan → Payment → Dashboard
Start with an Actor, add Feature / step nodes for significant stages, and use Decision nodes for meaningful branches. Separate checkout, onboarding, and publishing journeys when combining them would make the diagram difficult to follow.
Use Tracking for measurement requirements. State the event or outcome, its trigger, and relevant properties or consent requirements. Ordinary Step nodes should remain easy to read.
Map technical architecture
Represent responsibilities and direct dependencies:
- Stack: framework, runtime, or foundational technology choice.
- Service / module: a capability such as search, notifications, or billing.
- Datastore / CMS: where structured content or other data lives.
- Data model: an important entity or data shape.
- API / integration: a provider, hosted flow, or external interface.
- Decision, Note, and Constraint: reasoning, supporting details, and requirements.
Connect only relationships that help explain how the system works. Relationship meanings include flow, dependency, data, authentication, API, event, and constraint.
Explain and arrange the canvas
Use Title for a heading and Paragraph for explanatory text. Title width follows its content; paragraphs support line breaks and retain a minimum editable width. Both are annotations without connector handles.
Drag a node by its handle to move it. Use Shift-click or marquee selection to select several nodes and move a group. The subtle dotted grid helps alignment. Keep space between diagrams so their meaning and relationships remain clear.
Use the −, +, percentage reset, and Fit controls to navigate large plans. The minimap helps you move across the canvas. See Keyboard and canvas controls.
Collaboration and history
Live cursors and Selected, Editing, or Moving indicators show where teammates are working. They are coordination cues, not a reservation of the whole canvas. Different nodes can be edited concurrently; if a conflicting save is reported, preserve your changes and review the latest content before retrying.
Open History in the main header for the combined Structure canvas. A Structure restore replaces the saved graph content and layout while retaining page composition content. See History and restore scope before restoring.
Existing projects
When an editor opens an older project, its Structure, User Journeys, and Technical Architecture diagrams are brought onto this canvas. Their nodes and relationships are preserved, with the original arrangements placed apart to avoid overlap. You can then refine the layout like any other canvas.