Appearance
The outline
The Outline tab lists the page's sections and lets you rearrange them — carrying their content with them.
A section is a heading and everything under it, down to the next heading at the same level or above. That definition is the whole feature. A list that reordered headings while their paragraphs stayed put would be a trap, so the number of blocks a drag will carry is shown beside every line.
What you can do
- Drag a section to another position. Everything in it moves.
- Promote or demote it with the depth buttons. Subsections move by the same amount, so the shape inside the section survives.
Moving and re-levelling are separate gestures on purpose: where a section goes and how deep it sits are two decisions, and a drag only answers one.
Nothing about the list is stored
The outline is computed from the headings on every render, and every gesture produces a new block tree applied to the document like any ordinary edit. There is only ever one copy of the structure, so the list and the page cannot get out of step.
That also means the outline needs no export story, no fidelity tier and no place in the file. A view of a document is not part of it.
Because the edits go through the shared document rather than an API, peers watch them arrive live, the recorder derives move ops for blocks that already existed, and undo puts them back. A browser check asserts the block ids are unchanged afterwards — a rearranged page must not be a rewritten one, or the outline would quietly destroy the authored dates it moved.
Known limits
- No delete. Removing a line from a list looks like removing a line; removing a section removes every paragraph in it. Those two must not share a gesture.
- Top-level headings only. A heading inside a quote or a list item is part of that block's content and has no independent place to be moved to.
- A drop always lands above the section it was dropped on. There is no "make this a subsection of that" gesture — use the depth buttons, which say what they do.