Skip to main content
Pages can render Mermaid diagrams and supported diagram components. Use them to make relationships easier to understand alongside explanatory text.

​
Choose a diagram

A graph in a Page is authored content. It is not automatically a live map of every resource in the workspace. A wiki’s graph is a separate feature built from wiki links.

​
Example requests

Create a Page explaining our release process as a flowchart. Show review, approval, release, and rollback paths. Keep labels short and explain exceptions below the diagram.
Diagram the browser, API, database, and background worker. Label the requests and distinguish facts in the source from assumptions.
Map the dependencies between these milestones. Highlight anything that must happen before launch.
For a technical sequence, include the actors and the order of events. For a dependency graph, explain the direction of each arrow.

​
Make diagrams readable

Ask for one main idea per diagram, short labels, and a written summary. Split a large architecture into overview and detail views when needed. Diagrams follow the Page theme. Mermaid configuration overrides and external content are restricted; ask the agent to use the supported renderer rather than embed a remote diagram application.

​
Revise and discuss

Ask the Page’s author to update the diagram when relationships change. Select nearby explanatory text for a passage comment or use a general Page comment to refer to a named node or edge. A text comment does not automatically attach to a diagram node. Include the node or connection name in your feedback. For numeric graphs, see Charts and dashboards. For a maintained network of linked documents, see Wikis.