Pages and drafts

Everything you change in the editor goes into a draft. The live site keeps serving what it served before until you publish. That is the whole model, and almost every confusing moment in the editor comes from forgetting it.

​

Your draft is not the live site

Two consequences worth internalising:

• Opening the site in a normal browser tab shows the published page, not your edits. That is not a bug and it is not a caching problem. It is how you check whether publishing actually did anything.
• Your draft survives a reload, and a restart. It is held on the server, not in your browser tab. Closing the laptop does not lose the afternoon.

​

Switching pages

The Page control in the header lists every page your site declares. Pick one and the preview loads it; your chat history stays with you, but the draft you are editing is now that page’s. Each page keeps its own undo stack, so undoing on /pricing never disturbs /about.

​

Creating a page

Ask for it: “Create an /about page”. If the site defines page templates — named structures like Campaign landing page, set up in Site settings — you can name one, and the new page arrives with those sections already in place:

“Create a /spring-sale page from the Campaign landing page template”

Deleting a page is treated as destructive: the editor stops and asks before it does it, rather than doing it and offering an undo.

​

Languages

On a multilingual site the header carries a Language control alongside the page picker. Each language version of a page is edited as its own page — you switch to German, you edit German. Two entries in that list are not languages:

• Default — the site’s base language.
• Not language-specific — pages that exist once, in no particular language.

Asking the chat to “translate this page into German” fills the German version from the one you are on. It is also the single most expensive thing you can ask for, because it rewrites every text-bearing block on the page — see what things cost. More on how this is wired: multilingual and i18n.

​

Pulling from the site

Pull from site in the header re-reads the published content from your CMS or content files into the editor. You want it when someone changed the content somewhere other than Avocado — a developer edited a JSON file, a colleague published from your CMS — and the editor is still showing what it read earlier. It reports what it did (“Pulled 9 pages from site”), and it tells you plainly when there is nothing to read or the site is unreachable.

​

Sessions and site settings

A site in Avocado is a set of pages plus the settings that describe them — name, logo, hosting target, media source, and the editorial brief. The All sites control takes you back to the list, where each site shows whether it is currently reachable and whether its editing surface is fully working (Editing ready) or degraded (Limited editing). Limited editing means the site is not describing its blocks to the editor properly. Nothing you do will fix it from this screen; it goes to whoever maintains the integration, with coverage checks.

​

What to read next