Skip to main content

Pages And Project Docs

Pages keeps Markdown documents, notes, and diagram references inside Ideagram. This is product data, separate from this public documentation site.

Flow between Pages, diagrams, model, and MCP

The project is the shared boundary: Pages and Notes can describe or embed a diagram, while each diagram still owns its own components and connections. The architecture model is optional; when used, a diagram component can link to a reusable model entity. These links do not turn diagrams into one shared canvas. MCP reads and updates the same project context.

What Is Available​

  • Pages and notes are Markdown documents organized in folders. The underlying document model supports organization, workspace, and project scopes; the Pages panel works in the project currently selected in the app.
  • A Markdown editor and preview, document titles, and saved content.
  • Links to documents and diagrams, plus diagram embeds in the preview.
  • Project-scoped knowledge links between documents, diagrams, and model entities.
  • Decision records and specs through MCP, plus pending proposals and project questions.
  • Recoverable deletion of documents, notes, and folders through trash.

Create a Page or Note from Pages in the selected project. Give it a title, edit the body, and use Save. Follow the unsaved-changes prompt when navigating away. A page's title is also its name in navigation.

Folder names can contain spaces. Before deleting a folder, review the confirmation and affected items. Archive is a document status; deletion sends content to trash.

Diagram Embeds​

Use a wiki link to refer to a Page, Note, or diagram:

[[Architecture decision]]
[[diagram:Checkout flow]]

Put a diagram reference on its own line to render an embed. Add |live when you want the embed to load the current diagram when opened interactively:

[[diagram:Checkout flow]]
[[diagram:Checkout flow|live]]

Embeds show a preview when one is available. Select Interactive · zoom and pan to explore it, and use Open diagram to edit the diagram itself. Interacting with a preview does not edit the stored diagram.

Preview fidelity depends on the source and supported rendering features. Check Mermaid compatibility for imported content.

Status And MCP​

Documents have draft, published, and archived states. These are workflow states. Visibility is separate: new Pages and Notes are private by default and can be shared with the organization; access still also follows the document's scope and membership. See Drafts and publication.

An MCP client can discover your project with list_organizations, list_workspaces, and list_projects, then call get_project_context. See the tool reference for supported operations.

Confluence​

A built-in Confluence publishing or bidirectional-sync integration is not implemented. You can manually copy Markdown/Mermaid or use diagram exports in your team's publishing workflow. Automatic publishing, Atlassian OAuth, and conflict-aware synchronization remain future work.