About the docs graph

Explanation

Why the dashboard map exists, what it trades for paint caps, and how it relates to content gaps.

Context

The docs graph is a dashboard map of the live package: every folder, page, and section, and the links that connect them. It is rebuilt on every publish, so it reflects what is actually live rather than a separately maintained diagram.

Why

A list of pages hides structure. The map shows contains edges (the nav tree), link edges (what pages actually cite), and dashed semantic edges (related pages with no link). Reader signals and unanswered questions sit on the same picture so a gap is a place in the site, not a row in a spreadsheet.

Trade-offs

Large sites cap how much the canvas paints at once and tell you it is showing the busiest nodes (3D uses a tighter cap). Filters and search narrow in. Nothing is deleted; it is just not all drawn. 3D loads only when you open it so the rest of the dashboard stays light.

Further reading

*(see Reference: Analytics)* *(see How-to: How to invite teammates)* *(see Explanation: About graph engineering)*

What the graph shows

Nodes are the parts of your site: folders, pages, and sections, sized and colored so structure is readable at a glance. Edges are the relationships between them:

  • Contains edges follow your navigation tree, from folders down to pages and sections.
  • Link edges are the links your pages actually make to each other.
  • Semantic edges, drawn dashed, connect pages whose content is closely related even when nothing links them. They are inferred, and the dashed style marks them as such.

Above the canvas, a row of counts summarizes the version you are looking at: nodes, edges, pages, sections, and semantic connections.

Navigating the map

Use the 2D | 3D chips in the toolbar to switch canvas modes. 2D is the classic force layout with zoom, fit, trails, and PNG export. 3D is a cinematic WebGL force graph (orbit the camera, click a node to inspect); it loads only when you open it so the rest of the dashboard stays light. Fullscreen works in both modes. Click any node to drill into its neighborhood: its connected pages and sections load into the view and the map re-lays itself out. Filter chips let you show or hide node types and edge kinds, and a search box finds pages and sections by name; clicking a result centers the camera on it. Reset returns everything to the default view.

Tip
On a large site the canvas caps how much it draws at once and tells you it is showing the busiest nodes (3D uses a tighter paint cap for performance). Use the filters or search to narrow in; nothing is lost, it is just not all painted at the same time.

Version history

Every publish is an immutable version, and the graph keeps one map per version. When more than one version exists, a scrubber appears above the toolbar: drag it from oldest to newest to watch your documentation grow and restructure over time. The date and node count of the selected version are shown alongside.

Reader signals overlay

Turn on the overlay to recolor the map by where readers actually spend time, from quiet to busy. Pages with questions the assistant could not answer are flagged with a badge, and a side list groups those unanswered questions by the page a reader was on, most-affected pages first. It is the same signal as the content gaps view, seen in the context of your site's structure.

Note
Reader counts in the overlay are estimates, not exact totals, and the overlay has an honest empty state: before your site has traffic, it says so instead of drawing a blank heat map.

Doc trails

Doc trails are guided walks through the map. Pick a mode and press play, and the camera steps through the graph with a short narration at each stop:

  • Reading order follows your navigation from the start, the way a new reader would encounter the docs.
  • How it evolved steps through the story of your published versions.

Step with the on-screen controls or the arrow keys. A progress bar shows where you are, and you can stop the trail at any time to explore freely from wherever it left you.

Who can see it

The docs graph is available to workspace owners and admins, like the other insight views. See How to invite teammates. A brand new workspace shows the graph after its first publish; until then the panel says so plainly.

Engineering playbook

For the full knowledge-graph pipeline behind multi-agent systems (extraction, resolution, assembly, multi-hop querying, evaluation, and production checklists), read the Graph engineering playbook. That page includes reconstructed figures and maps each stage onto this product graph, Sources sync, Knowledge search, and Doc Trails.