Preview, publish and roll back

Drafts, preview in your real design, immutable revisions, scheduled publishing and rollback.

Drafts

Every change in Studio is a draft first. Drafts are never returned by the published Delivery API, so they cannot leak onto your website by accident.

Preview

Editors can see a draft in three ways:

Website view in the page editor shows your real website in a frame next to the fields.
Full-screen preview and pop-out show the draft at different screen sizes.
Preview on website opens your website’s preview route with a one-time link valid for 15 minutes.

Preview needs a preview route on your website (see Connect a Next.js website) and works in Development only. Drafts are always served with noindex and never cached.

Click-to-edit

Optionally, editors can click a section on the previewed page to select it in Studio. In draft preview only, your website:

puts data-atlas-section-id="<section id>" on each section’s element;
posts { type: 'atlas:ready' } to the parent window when it runs inside a frame;
on a click, prevents navigation and posts { type: 'atlas:select', sectionId };
outlines the section named in { type: 'atlas:highlight', sectionId }.

Only accept messages from, and only send messages to, the Studio origin. None of this runs outside preview.

Publish

Publishing creates an immutable revision. Your website sees it on its next request, or immediately when you use webhooks. Before publishing, Studio lists any publish problems (for example a required field left empty), and the page cannot be published until they are fixed.

Editorial collections (news, articles) also support scheduled publishing, slugs and an RSS feed.

Roll back

In Development, restore an earlier revision of a page and publish it again.
In Production, roll back to an earlier release. This needs the rollback permission.

A rollback is itself a new, recorded event. Nothing is deleted.