Opening a page from the Design tab’s tree loads it at /pages/<id>, and everything you need is on that one screen. It has three regions: a two-row document header telling you what you are looking at and giving you the controls to change it, the canvas where you write, and a right rail of five tabs holding everything about the page that is not the page’s words. The same canvas serves your documentation sets at /documentation/<id>, so a docs page and a blog post are edited in exactly the same place.
Two things to settle before the tour, because both surprise people who arrive from other tools. There is no Save button. Every keystroke, every block edit and every settings change persists as you make it — what you see is what is stored. And saving is not publishing: nothing you do here reaches your live site until you publish, which is a separate, deliberate act described in how publishing works.
Row 1: what page am I on
The top row is identity on the left and action on the right. Nothing in it edits your content.
| Element | What it tells you | When it is hidden |
|---|---|---|
| Title | The page’s title, or Untitled Page if it has none yet | Never |
| Pencil | Opens the Edit page title dialog | When you have no edit permission on this page |
| Version chip | v1, v2, v3 — how many times this page has been through a publish cycle. A closed padlock appears beside the number once the version is published, with the tooltip Page is locked (read-only) | Before the first version exists |
| Status badge | The current revision’s state — see below | Never |
| Path | The page’s live URL path, in a monospaced line under the title | When the page has no resolvable path yet |
| Presence avatars | One per person in the page right now | When you are alone in it |
| Mode selector | Editing · Suggesting · Viewing | Shown in row 1 only in read-only states; otherwise it lives at the right end of the toolbar |
| Publish / Revise / Scheduled for… | The publish control, which changes shape with the page’s state | In the read-only analytics view; when you lack publish permission and the page is not scheduled; and on a published API page |
| Badge | Color | Meaning |
|---|---|---|
DRAFT | Zinc | Never published. Nothing about it is public |
IN REVISION | Orange | Previously published and unlocked for editing. The published version is still live and unchanged |
SCHEDULED | Violet | Queued to publish at a set time |
PUBLISHED | Green | Live, and locked. The publish date and time sit beside the badge |
The version chip and the status badge answer different questions and it is worth keeping them apart: the badge says what is happening to the page now, the chip says how many published versions are behind it. A page reading v3 with an IN REVISION badge has three published versions, the third of which readers can see, and a fourth being written. Revisions, versions and reverting follows that thread all the way through.
Row 2: the toolbar
The second row is the editor’s formatting toolbar — the real menu bar, not a summary of it. It is the only way to produce formatting in Leed: there are no markdown shortcuts to type. Every control on it, its keyboard shortcut and the markup it writes are enumerated on the editor toolbar reference, and what each inserted block then lets you configure is on block types and block settings.
In a read-only state the toolbar renders nothing at all — row 2 is empty, not disabled. That is the fastest way to tell at a glance whether you are looking at a page you can change.
The canvas
The middle of the screen is a live rich-text surface, not a text box with a preview beside it. An alert renders as an alert, a table as a table, a Mermaid diagram as the drawn diagram, a code block with its syntax highlighted — each one the shape it will take on your site. Click into a widget and it opens for editing; click out and it renders again.
Before the editor appears
The canvas is collaborative, so it has to connect before it can be edited, and you will meet two states while that happens.
Connecting… means the document is still syncing. It is normally too brief to read, and it resolves on its own.
Unable to connect to the collaborative editing service. Please refresh the page. means the connection failed outright. Refreshing is the fix, and it is genuinely the fix — the message is not a placeholder for a lost draft, because nothing you had already typed was held only in the browser. What is happening underneath, and what the presence avatars are actually showing you, is on autosave, collaboration and locking.
The right rail
Down the right edge runs a 40-pixel strip of five icons. Clicking one opens a drawer beside it; clicking the icon of the tab already open closes the drawer again. The drawer is resizable between 240 and 600 pixels by dragging its left edge, and each tab remembers its own width, so the Assistant can be wide for a conversation while Page settings stays narrow.
The five tabs
| Tab | What it does | Where it is documented |
|---|---|---|
| Assistant | An AI conversation scoped to this page, marked with a sparkle and an “AI” badge | AI help in the editor |
| Comments | Threaded comments anchored to blocks, plus emoji reactions | Comments and reactions |
| Workflows | What happens when this page is published — email and social channels, share buttons | Page workflows and distribution channels |
| Analytics | Traffic and engagement for this page, with its own filters | Page analytics in the editor |
| Page settings | Slug, summary, keywords, authors, labels, redirects, permissions, delete | Page settings |
Two of the five carry gates that belong to other parts of the product rather than to the editor. On the Workflows tab, the email channel needs Starter and the social channels need Growth, and below the floor the tab is an upgrade panel rather than a list of switches. On the Analytics tab, the attribution block needs Growth; the rest of the tab is not gated.
Which tab opens by itself
Leed picks the opening tab from the state of the page, on the theory that the useful panel differs between a page that does not exist yet and one thousands of people are reading.
| Page state | Tab | Drawer open? |
|---|---|---|
| Brand new, just created | Page settings | Yes |
| Live — published at least once, or a site-builder page | Analytics | Yes |
| Unpublished, and the last tab you used was Analytics | — | No — the drawer closes |
| Anything else | The tab you last used | As you left it |
The third row is the one worth understanding: analytics for a page nobody can reach is an empty panel, so rather than show you nothing, Leed gives the space back to the canvas.
Read-only and near-read-only states
Four separate things can make the editor read-only, and they look similar without being the same. In all four, the toolbar in row 2 disappears and the mode selector moves up into row 1.
Published and locked. A published version is frozen. The version chip shows a padlock, the mode selector is disabled with the tooltip Locked: Readonly, and the publish control reads Revise. Pressing Revise starts a new version — the published one stays live and unchanged while you work on it.
No edit permission. If your role or the page’s overrides do not let you edit this page, the mode selector is disabled with the tooltip View Only: No edit permissions and there is no pencil beside the title. You can still read the page, and you can still comment on it.
The read-only analytics view. Analytics for a published page cannot be shown while you are editing it, so the Analytics tab offers a View Analytics button that switches the whole editor into a read-only view with a blue Read-only analytics view strip across the top. Back to Editing in that strip returns you.
Everything else on this screen is covered by a page of its own. The tree you arrived through is managing pages; the mode selector’s Suggesting setting is suggesting mode and tracked changes; and links, media and blocks each have their own reference, reached from the toolbar page above.