Previewing, saving, and publishing

Documentation / Getting started

A preview shows a particular content state. A saved draft preserves edits without necessarily replacing the live page. Publication commits the reviewed page state. Do not use these terms as synonyms, and do not assume every Beeboo editing surface uses the same save process.

Managed page editing

Where cloud recovery is available, the managed editor saves recoverable page edits separately from the live page. Its status indicator reports saving problems. Publishing a draft commits the complete accumulated draft, not only the text changed most recently.

Review the saved draft before publishing. Check headings, links, media, layout, and the selected language. If a save reports a conflict or failure, keep the current content available and resolve the problem before assuming it is stored.

Template editing and shared footer editing have separate save paths. A page-settings save also differs from the managed body's draft recovery. Saving a site-wide setting can affect several pages immediately, so check the scope of the control you are using.

Custom source and shared shells

Custom source saves use revision checks and do not follow the native body's cloud-autosave path. Custom scope changes use explicit draft, review, and publication controls. Shared shells add a further distinction: publishing an immutable shell revision does not activate it for the site.

Verify as a visitor

After committing a change, open the normal page address without a draft preview parameter. Check it signed out when access behavior is involved. Reload the CMS state if necessary to confirm the stored result rather than relying on an unsaved editor preview.

For recovery, conflicts, and revisions, continue with Saving, recovery, and troubleshooting.