Pages

Pages are rich documents that live inside your project, next to the work they describe: specs, meeting notes, runbooks, decision records, onboarding guides.

Work items are the what. Pages are the why.

Pages are switched on per project (Project settings → Features → Pages).

What you can do

  • Write documents in a full editor — headings, lists, to-do lists, tables, code blocks, callouts, images, colours.
  • Keep a page private to you or public to the project.
  • Lock a page so it stops being edited.
  • Navigate long pages with an automatic outline.
  • Duplicate, move, archive and export pages.
  • Restore an earlier version from page history.

Getting started

Create a page

  1. Open a project and click Pages in the sidebar (shortcut G D).
  2. Click the create button, or press N then D from anywhere in the project.
  3. Give it a title, optionally pick an emoji or icon, and set its access:
    • Public — everyone on the project can find and read it.
    • Private — only you.
  4. Create it, and start typing.

📷 Screenshot: the create-page dialog with title, icon picker and the public/private access toggle.

The editor

Start typing. The page saves as you go — there's no save button.

Press / on an empty line to open the command menu. That's the whole interface. From it you get:

  • Text and headings — H1 through H6
  • Bulleted list, numbered list, to-do list (real checkboxes)
  • Table
  • Quote
  • Code block
  • Callout — for the things people skim past and shouldn't
  • Divider
  • Image
  • Emoji
  • Text colour and background colour

Select text to get an inline formatting toolbar — bold, italic, links and the rest. Standard shortcuts work (Cmd/Ctrl + B, I). Markdown-style typing works too: # then space for a heading, - then space for a bullet.

Drag and drop an image straight into the page to upload it.

📷 Screenshot: a page with the / command menu open, showing headings, lists, table, code block and callout.

Linking to work items

Pages and work items are meant to point at each other.

From a work item to a page: copy the page's link (Copy link in the page's … menu) and add it as a link on the work item, or drop it in the description.

From a page to a work item: open the work item, use Copy link from its context menu, and paste the URL into your page. Anyone reading the spec can get straight to the work.

A common pattern: one page per feature, holding the spec and the decisions, with its link attached to the parent work item — and the module or cycle named the same thing.

Organising pages

The Pages list separates public pages from your private ones, and gives you archived pages too. Search and filter from the top of the list.

Each page's … menu gives you:

  • Lock / unlock — freezes the content. Nobody can edit a locked page until it's unlocked. Use it on anything that's been agreed: a signed-off spec, a postmortem.
  • Make public / make private — switch access after the fact.
  • Copy link
  • Open in new tab
  • Make a copy — duplicate the page, for templates and recurring notes.
  • Move — send the page to another project.
  • Archive / restore — take it out of the list without losing it.
  • Delete
  • Export

📷 Screenshot: the Pages list with public and private sections, and a page's … menu open.

The navigation pane

Open a page and you get a side pane with:

  • Outline — every heading, as a clickable table of contents. This is why you should use real headings rather than bold text.
  • Assets — the images and files used on the page.
  • Info — page metadata.

Version history

Pages are versioned as you edit. Open the history to read an earlier version and restore it if you need to. Nothing you write is truly lost.

Tips

  • Structure with headings, not bold text. The outline pane is generated from headings, and a page with none is a wall.
  • Lock the page when the decision is made. A spec that quietly changes after sign-off is worse than no spec.
  • Make a copy is your template mechanism. Write one good meeting-notes page, duplicate it every week.
  • Keep private pages for genuine drafts. A spec that nobody can find isn't a spec.
  • Use callouts for the one thing readers must not miss. Use them once per page; two callouts are zero callouts.

Limits & good to know

  • Pages are per-project. A page belongs to one project, though you can move it to another.
  • Private means private. Other people — including admins — don't see your private pages in the list.
  • A locked page can't be edited by anyone, including you, until it's unlocked.
  • Pages don't render work items as live, self-updating cards in the core editor — paste the work item's link and the reader can click through.
  • Pages are documents, not a database. If you find yourself keeping a table of tasks in a page, those are work items.