Docs Guide

Glacier includes a rich-text document editor. Docs live alongside your board — either scoped to a single project or shared across the whole workspace. Claude can read, write, and update docs via MCP.

Project docs vs workspace docs

Project docs are scoped to a specific project. Access them via the Docs tab at the top of a project. Use them for specs, decisions, architecture notes, and context that belongs to one project.

Workspace docs are shared across all projects. Access them via the Docs section in the sidebar. Use them for team norms, runbooks, onboarding guides, and reference content that Claude should always have access to regardless of which project it's working in.

Both types use the same editor and support the same features.

Creating a doc

• Project doc: Open the Docs tab → click + New doc.
• Workspace doc: Click Docs in the sidebar → + New doc.

Docs save automatically as you type. A save indicator appears in the top-right corner of the editor.

The editor

The Glacier doc editor is a block-based rich text editor powered by Tiptap. Each paragraph, heading, list, and code block is an independent block.

Slash commands

Type / on a new line to open the slash command menu. Available blocks:

Inline formatting

Select any text to reveal the formatting toolbar:

• Bold (⌘B), Italic (⌘I), Strikethrough (⌘⇧X), Code (⌘E)
• Highlight (⌘⇧H)

Links

Select text → click the link icon in the toolbar → paste a URL. Links open in a new tab.

Linking docs to cards

Docs and cards can be linked together. This connection is bidirectional:

• From a card detail panel → Link doc → search for a doc by title.
• From inside a doc → the linked cards section shows all cards that reference this doc.

Claude can follow these links via MCP. Ask it to:

"Summarise the doc linked to PROJ-7." "Update the doc linked to GLACIE-12 with a summary of what was implemented."

A doc can be linked to multiple cards. This is useful for shared specs or decision records that span several work items.

Docs sidebar and scope label

The sidebar doc tree shows both workspace docs and project docs. When a workspace and project share the same name, project-level docs show a scope label to distinguish them from workspace docs.

Docs and Claude

Because workspace docs are always accessible via MCP regardless of which project Claude is working in, they're the right place for:

• Team conventions Claude should follow when creating cards
• Glossaries and domain terminology
• Runbooks Claude can reference when troubleshooting

For project-specific context, use project docs and link them to relevant cards.