Adding the filter empties the site until you backfill. Entries created before the field exists have no value for it, and an equality clause never matches a missing field — so every listing goes blank the moment you save the query. Write the value explicitly on every existing entry; a default: only applies to rows created afterwards.
## 3. Publish the pages
Publishing creates a live revision. An unpublished page keeps serving its previous revision, or 404s if it never had one.
It is one button, top right of the page editor, sitting next to **Edit** and **Preview** — and it acts on **the page you are looking at**, one at a time. The header beside it names what you are about to publish: the page, and under it the path it will answer on, locale included.
Two things in the left-hand tree are worth reading while you are there, because they are the states this guide keeps talking about:
- **A crossed-out eye marks a hidden page** — `visible: false`, active and routable, simply absent from the menus. Here that is *Merci*, *Kit de contenu* and *Formats pro*.
- **A hidden page nested under its listing is a collection's detail page.** *Saveur*, indented under *Saveurs*, is the single page that serves every flavour in the collection. One page, one URL pattern, every entry. See [Build a blog](/en/docs/blog), section 4.
**Two shortcuts the editor does not show you**, because neither lives in it. Right-clicking a page in the tree offers **Publish** without opening it. And the tree's own dropdown — the caret next to the menu's name, not the page — carries **Publish all**, which is what you reach for after building several pages in one sitting.
Publishing everything at once is a convenience, not a different operation: each page still gets its own live revision. It is also the moment the warning below stops being theoretical — *publish all* means the pages you had not finished thinking about, too.
State is not publication. state: active means routable, not online. An inactive page 404s everywhere, including on your machine. Never deactivate a page to "hide it while working".
This is the step not to delegate. Other guides here end with a prompt you can hand to an agent. This one deliberately does not. The tool exists — publish-page — which is precisely why the rule needs stating: publishing is what makes a page visible to the world, and an agent has no way to know whether the copy was signed off, whether the photographer was paid, or whether today is the day. The rule the skill library gives agents is the same one, in one line: nothing publishes itself.
And there is nothing to delegate *before* it either, because the agent cannot see the ground truth.
Publication state is not exposed to an agent. Measured on Lisière: neither get-navigations-with-pages nor get-page-with-content returns anything about publishing. A page comes back with state, visible and an updated_at — there is no published-at, no revision number, no "live version differs from draft" flag. So "list the pages waiting to be published" has no answer, and an agent asked for one will produce a plausible list built from state, which is a different thing entirely. Read the tree in the back-office instead: publish page by page, or use Publish all.
## 4. Point the domain at the site
Domains live in the site's own **Domains** screen, next to Overview and Collaborators. Add the hostname there, and the panel tells you what to create at your registrar and where the check currently stands.
**Every site already has an address**, before any of this: `