Skip to content
Docs

Page editor

The editor's 8 steps across 3 phases: Brief It, Write It, Ship It, with a review pass in between.

Open in ChatGPTOpen in Claude

App route: /page_briefs/{id}

The page editor at the Write it step, with the 8 steps down the rail
The page editor at the Write it step, with the 8 steps down the rail

The page editor is where a brief, the plan for one page, becomes the page itself. It runs as 8 steps across 3 phases (brief it, write it, ship it), with an agent(an automated worker) doing the production and you steering at each handoff.

Doing this rather than looking it up? The Tutorial walks this screen step by step in 5.2 · The briefing process.

Reference

Annotation scope: 3 answers to one question, "Should we learn from this for next time?" An annotation is a note you leave on a draft saying what is off and why, instead of silently rewriting it. The composer has no type picker, only that question: leave it on Decide for me and the agent learns the note once the same point repeats, pick No, one-off for a fix to this article only, or pick Yes, learn it to make the note a standing rule for future drafts once it folds into the writing profile, the compiled version of how you sound. Notes you save as a workspace member show their scope underneath; notes left through a guest review link do not.

Annotations train nothing until the profile updates. They accumulate as pending feedback and fold into the writing profile when their review is completed, or when someone clicks Update Writing Profile on Writing Profile. Completing a review schedules that update on its own; the rewrite dialog has no switch to defer it.

Content templates decide the funnel stage, the outline structure, the post-processing an agent runs after drafting, and which agents run at all. You can create your own; the stock set is a starting point rather than a fixed menu.

A template is not a page type. Page type classifies pages that already exist. A template is an input that shapes one you're making.

Metadata fields set at Ship it: title, meta title, meta description and slug, plus the article's author when the collection you publish to has an author field mapped. Meta title and description carry the usual length guidance.

Sharing for review issues a link that invites someone by email. External reviewers annotate in the same surface your team does, but they cannot set a note's scope.

Why it works this way

On this page