Sign InGet Started

Organizing Blueprints

Build a clear document hierarchy, navigate between blueprints quickly, and keep your organizational knowledge structured as it grows.

Overview

Blueprints are organized as a tree of documents. Each workspace has one root-level entry point, and every other document is a child — or grandchild — of an existing one. The navigation panel on the left side of the editor displays the full tree and gives you direct access to every document in your blueprint library. As your content grows, you can rearrange the structure by moving documents to different parents, or keep the sidebar collapsed for a distraction-free editing experience.

Blueprint navigation tree showing a hierarchical document structure with nested sections

How It Works

  1. See the full tree — The navigation panel shows all your blueprint documents in a collapsible tree. Root documents appear at the top. Child documents are nested beneath their parents and can be expanded or collapsed individually.

  2. Navigate between documents — Click any document in the tree to open it. The editor switches to that document immediately without a full page reload. Your scroll position and the state of the tree persist across navigation.

  3. Expand and collapse branches — Documents with children show a chevron. Click it to expand or collapse that branch. Collapsed branches still navigate correctly — clicking the document title opens it even when the children are hidden.

  4. Move a document — To change where a document sits in the hierarchy, use drag-and-drop in the navigation tree. Drag a document node and drop it onto the new parent. The tree updates immediately and the change saves automatically.

  5. Delete a document — Hover over a document in the tree to reveal its context menu (the three-dot icon). Select Delete to remove it. If the document has children, they are removed along with it. You will be redirected to the parent document or to the blueprints list if the deleted document was a root.

  6. Collapse the navigation panel — Click the collapse toggle in the document header to hide the tree sidebar. In this mode, the sidebar shrinks to a narrow icon strip. Click the toggle again to expand it back to full width. Your preference is remembered across sessions.

Key Capabilities

  • Hierarchical tree navigation: All blueprint documents are visible in a single panel. The tree supports unlimited nesting depth. Folder icons indicate documents with children; file icons indicate leaf documents.

  • Drag-and-drop reordering: Move any document to a different position in the tree, including changing its parent. The order within a level reflects creation order by default.

  • Breadcrumb context: When you open a deeply nested document, breadcrumbs at the top of the editor show the full path from the root. Clicking any breadcrumb item navigates to that ancestor.

  • Real-time tree updates: If a teammate creates, renames, or deletes a blueprint while you have the section open, the navigation tree updates automatically. You do not need to refresh.

  • Collapsible sidebar: The navigation panel can be toggled between full-width and icon-only modes. On screens narrower than 1280px, it collapses automatically to give more space to the document content.

  • Inline create from the tree: Hover over any document in the navigation tree and click the plus icon to create a child document directly beneath it. The new document opens immediately with its title focused for editing.

  • Delete from context menu: The three-dot menu on each tree item includes a Delete option, so you can remove documents without opening them first.

Structuring Your Blueprint

There is no required structure. The right organization depends on what your team needs to document. A few patterns that work well:

  • Flat top-level documents: One document per major topic (Vision, Strategy, Personas, Voice & Tone). Works well when topics are relatively independent.

  • Topic with sub-sections: A root document per domain, with child documents for each sub-topic. For example, "Product Strategy" as a root, with "Current Quarter", "Roadmap", and "Principles" as children.

  • Reference library: A mix of evergreen documents (Company Mission, Personas) and frequently updated ones (Current Focus, OKRs). Both types live in the same tree.

Tips

  • Keep the top level of the tree shallow. Two to four root-level sections is usually enough. Deeper hierarchies are better represented as nested children rather than more roots.
  • Name documents with enough specificity to be scannable in the tree. "Q1 Strategy" is easier to find at a glance than "Strategy Notes".
  • Use the collapse toggle when writing long documents. Hiding the tree gives more horizontal space to the editor content.
  • The AI references all your blueprint content regardless of how it is structured. You do not need to put everything in one document — a well-organized tree works just as well.

Related