Publishing in depth

What counts as a change, how publishing some pages and not others works, reverting single changes, versions and Undo publish, review link versus live site, and what goes out with each publish.

This continues Publish your site.

What's in the list

The panel lists changes by page, and each page by section. A change says what it is, in a designer's words:

• Text — "Text “Book now” → “Book a flight”", the old text struck through.
• Style — the element's name from Layers, the property and the value: "Hero shade · Opacity 1 → 0.6", "… · Z-index 2 · Tablet", with a color swatch where it helps.
• Images, added and removed elements, links and code.

What every page shares sits under Whole site: colors and fonts, the layout, the navigation and other sections used on several pages ("Navbar · on 4 pages"), and settings. Breakpoint widths change every page, so Whole site can't be left out when they changed.

Each change has:

• ↩ — revert just this change. It's one step, with Undo in the message.
• → — open the page and select the element.

Show code changes in the panel's ⋯ adds the exact difference in the code under each group.

Publishing only some pages

Untick a page and its changes stay out of this publish. Tandmade builds the site from a temporary copy without them; your working copy in the editor isn't touched, and you can keep editing while it runs. The unticked changes wait in the panel for the next publish.

The very first publish of a site goes out whole, so the live site never links to a page that isn't there.

Two places to publish

With a domain, the panel counts changes against what's live on the domain. Publishing to the review link doesn't reset them, and the panel says when The review link is ahead.

Versions

Every publish is saved as a version.

• Undo publish, right after publishing, puts the previous version back live and keeps your edits waiting in the editor.
• Earlier versions… in the panel's ⋯ lists older versions, when and where they went. Restoring one puts the site's pages, sections and styles back as they were, as one step you can undo. It goes live with your next publish.

Restoring a version doesn't change your collection items or uploaded media; they have their own history. See Write and format content.

What goes out with a publish

• Pages, sections, styles, your brand's tokens and files, and the navigation.
• Site settings: name, icon, SEO defaults, indexing, integrations and custom code. See Site settings.
• Redirects, including the 301s added when you moved a page.

What doesn't wait for a publish: collection items and their SEO, which go live when you publish them in Content.

While it runs

The steps tick off one by one: building, uploading (with file counts, "12 of 40 new files"), connecting the address. Each step shows how long it took. A closed tab doesn't stop it; the Publish button shows a small running line, then Live for a few seconds.

When a build fails

The line stops at the failed step and turns red. Try again, Show details for the build log, or Fix with agent, which opens the agent with the problem written in. Your live site stays as it was until a publish succeeds.

Visitors get

Pre-rendered pages, collection pages from the cache at the edge of Cloudflare's network, and images in AVIF or WebP at the size each screen needs.