There is no page list in Leed. The rail tab Design opens the editor, and the editor’s left panel is the list — a folder tree of every page on your site that stays on screen while you work. Opening Design with nothing selected lands you on /pages, which is that panel beside an empty stage; clicking a row loads the page at /pages/<id> without the panel ever reloading. (An old /library link still works: it redirects to /pages.)
Where the page tree lives
The left panel is shared by seven libraries, and the tree in this page is what you get when the picker at the top reads Site. Above the tree sit a search box and a row holding that picker, a filter button and the ＋ button; below it, the tree itself. All of it is described once, for all seven sections, in the Design workspace — this page covers what the Site section does that the others do not.
Two behaviors are worth knowing before you start clicking. The panel’s right edge is a drag handle labeled Resize left panel, and each section remembers its own width, so a deep page hierarchy can have 500 pixels while Forms keeps the 320-pixel default. And switching away and back returns you to the last page you opened this browser session — never to a page you did not choose, and never to the first row in the tree.
Reading the tree
Folders in the tree are not something you create. They are the segments of your pages’ URL paths: a page at /docs/editing-pages/managing-pages/ puts a docs folder inside the root, an editing-pages folder inside that, and the page itself at the bottom. Change a page’s path and it moves in the tree; there is no separate “move to folder” action. Where a folder’s own path is also a real page — /blog/ being both a folder of posts and a landing page — the folder row is clickable and opens that page. The / (homepage) row at the very top is your site root, and the control beside it expands or collapses the whole tree at once.
Which folders you have open is remembered for the browser session, and the ancestors of whatever page you navigate to are added to that set automatically, so a page you reach by link or by search is always visible in context rather than buried in a collapsed branch.
Status icons
Every row carries a glyph on the left telling you where that page stands. It reflects the page’s current state, not the state of anything you can see on the live site — a published page you are revising still shows the published icon until the revision is published in turn.
| Icon | Meaning | What you can do with it |
|---|---|---|
| Blue page | Published — a version of this page is live | Read it; press Revise to unlock it for editing |
| Slate page with an orange mark | Unpublished — a draft, or a revision that has not been published | Edit it freely; nothing you type is public |
| Slate clock | Scheduled — queued to publish at a set time | Edit it, or open the schedule to change or cancel the time |
| Teal document | Site builder — served from your repository, not stored in the CMS | Open it to read; edit it in the repository |
Search, sort and filter
The search box matches both the title and the path, so typing editing-pages finds a folder’s worth of pages and typing part of a title finds one. While anything is matching, folders holding a match are forced open so results are never hidden behind a collapsed chevron. The box empties when you switch sections — it belongs to the panel rather than to the tree — so a query you left in Forms is gone by the time you come back to Site.
The filter button beside the picker opens the rest of the controls, and it darkens when any of them is off its default. Toggling a pill does not close the menu, so you can build a filter up in one pass.
| Control | Values | Persisted? |
|---|---|---|
| Sort | Name · Created · Published, each ascending or descending. Default Published, newest first. Pages missing that date always sort last, whichever direction you pick | Browser session |
| My pages | On or off. On means you are an author, a contributor, the creator or the last editor of the page | Browser session |
| Status | Published · Scheduled · Approved · In Revision · Draft · Site Builder. Any number at once; none selected means no status filter | Browser session |
| Type | One pill per page type in your workspace. Site-builder rows have no page type, so any type filter hides them | Browser session |
| Search | Free text, matched against title and path | Cleared on section switch |
Everything here is scoped to the browser session, not to your account: a new window or a reload starts from the defaults, and the filter you left running yesterday is not waiting for you.
What “Approved” means today
Approved is in the status list because APPROVED is a real revision state that the publishing machinery recognizes — a page in it is editable and schedulable exactly like a draft. What does not exist is any control that puts a page into it. No button in the CMS sets Approved, so unless something has written the state through the API, the facet matches nothing. Treat it as reserved rather than broken, and read the honest account of what approval does and does not do today on publishing and scheduling a page.
Creating a page
The ＋ button above the tree opens the New Page dialog. It asks for three things and then gets out of the way.
| Field | Required | Constraint | Where you change it later |
|---|---|---|---|
| Page Name | Yes | 2–150 characters. Rejected below two with Minimum 2 characters, above 150 with Maximum 150 characters | The pencil beside the title in the editor |
| Page Type | Yes | One of your page types; locked types are not offered | Page settings → Page Type |
| Labels | No | Any number of existing labels; you cannot create one here | Page settings → Labels |
There is no slug field. The slug is derived from the Page Name, and the page’s URL is that slug under the page type’s own path — so the Page Type you choose decides more than the layout. It sets where the page lives, which formatting controls the editor shows you, and which metadata fields the page must fill in before it can be published; page types covers the whole of that, and URL paths and slugs covers how the path is assembled. Labels are worth setting early even though they are optional, because they do three separate jobs — grouping, series and access — described in labels and series.
Submit creates the page and opens it, with the right rail already showing Page settings — the one moment Leed volunteers that panel, because a brand-new page is the moment its slug, summary and dates matter most.
New pages start empty
Leed has no content templates. There is no “start from” option in the New Page dialog and no library of skeletons to pick from, and this is not an oversight to work around — a page’s frame, navigation and styling all come from its page type and layout, so an empty draft still publishes as a fully formed page. When you genuinely want the same structure twice, there are three real options:
- Copy the blocks. Open a page shaped the way you want, select the blocks, copy, paste into the new draft. Structure comes across intact because every block is Leed Markdown underneath.
- Ask the assistant to scaffold it. The Assistant tab can lay out a page to match one you point it at; see AI help in the editor.
- Push the repetition into the layout. If every page of a type needs the same banner or footer block, that belongs in the layout, and then no page has to carry it at all.
Renaming
The pencil beside the title in the editor opens the Edit page title dialog. It changes the title — the words in the tree, the heading on the published page, the <title> tag — and nothing else. The slug does not follow it. Renaming Q3 Launch Notes to Q4 Launch Notes leaves the page at /blog/q3-launch-notes/, which is usually what you want mid-flight and occasionally not. Changing the URL is a separate, deliberate act on the Slug field in page settings, and it is deliberate because the old URL stops working unless you keep it alive through aliases and redirects.
Pages you cannot see
The tree is filtered by permission, so two people on the same workspace can see different trees.
A member whose role is Restricted sees nothing by default. Their tree contains only the pages reached through an access override — one on a page type, one on an individual page, or one on a label the page carries — and every other page is simply absent rather than grayed out. Who can see what sets out the whole model, including how those overrides are granted.
Separately, and for every role including Administrator, a page marked private is listed only for the person who created it. Nothing in the CMS marks a page private — the field is set through the API or an MCP client — so if a page is missing from your tree and you are not Restricted, private pages is where the explanation lives.
Deleting a page
Delete lives at the bottom of the Page settings tab in the editor’s right rail, not in the tree. What happens when you press it depends entirely on whether the page has ever been published.
A page that has never been published is a plain confirmation — Are you sure you want to delete this page? — and is then gone for good.
A published page opens the Delete Published Page dialog, and it will not let you go ahead until you have said what the live URL should do afterwards. Choose a page from the redirect picker, or tick Show “404 Page Not Found” instead of redirecting. The Delete button stays disabled until one of the two is true.
If the outcome you choose would break the URL — an unpublished page, or a published one where you ticked the 404 box — the dialog also lists every menu the page appears in, with the number of items each contains, and removes it from those menus as part of the delete. Pick a redirect instead and the menu entries are left alone, because the URL they point at still resolves.
The deletion itself rides the same pipeline as a publish: the page leaves the CMS immediately, and it leaves your live site on the next build. Nothing is instant, because nothing on your site is — see how publishing works.
There is no Unpublish
Nothing in Leed takes a live page down and leaves it in your drafts. There is no Unpublish button, no hidden toggle and no plan tier that adds one. Taking a page off the live site means deleting it, with either a redirect or a 404 — and the “Scheduled for publishing” panel deliberately never lists a pending deletion, so do not go looking there for confirmation.
If what you actually want is to change a live page without readers seeing the work in progress, that is not deletion at all: press Revise and the published version stays live, untouched, while you edit the new one. The page editor shows where that control sits, and core concepts explains why a page, a revision and a published version are three different things — the tree only reads correctly once they are.