Content Management that can withstand the plundering hoards

Publishing and rolling back

Drafts are editable pages, settings, themes and media on private CMS storage. A release is the generated static site on published storage. The public frontend serves the active release without reading the private project.

What becomes public

A publication includes every saved page enabled for publication, site settings, the selected theme and uploaded assets. Disabled pages are omitted, including from navigation and generated listings; their editable drafts remain in the CMS. Menu visibility controls navigation; choose Publish when the whole saved site is ready to go live. Review imported private posts, hidden pages and unused media before publishing.

The top-right Publish site action saves the currently open page before publishing the entire saved project. Save settings and theme workspace changes explicitly; unsaved work in another tab is not part of the snapshot. If the current draft cannot be saved, publishing is cancelled.

Publish

  1. Preview content, links, menu and images. A page preview includes that page's unsaved edits; other pages and theme preview site content use saved drafts.
  2. Select Publish and wait for success. Avoid closing the tab while waiting.
  3. Record the release number and check the public homepage and affected URLs.

Publication builds a new directory, renders/sanitizes content, copies media, creates sitemap/robots files and activates the complete release by moving a filesystem pointer. Files in an active release are not edited in place. With default frontend settings the pointer is refreshed about once a second.

If publishing reports an error, read the current release status and inspect the public site before retrying. Most failures leave the old release active, but a late storage/history error can be reported after the new pointer has moved. Give the administrator the error, time and displayed release number.

Roll back the public site

Your administrator chooses how many historical releases to retain. The default is zero history after a short cleanup grace period. If a retained release is available, Roll back offers the previous activation when available, otherwise the newest other retained release. Read and confirm the offered release number. An expired release cannot be restored through this action.

Rollback reactivates generated files without rerendering. It does not undo page edits, restore deleted drafts or change your saved theme/settings. A later Publish uses the current saved drafts again. To undo a source edit, change the draft and republish, or ask the administrator about restoring a storage backup. Publish and rollback use the same permission gate; a forbidden response needs an administrator to check your roles.

A browser refresh may still use cached resources. Retry after a short delay, then compare in a private browser window. Ask the administrator to investigate ingress/CDN caching if the release number has changed but the public content has not. Arrange redirects with your administrator when page URLs change.

Deleting a draft, asset or theme does not erase copies already in retained releases or external caches. Public release history is not a backup of editable source. Backup and restore is an administrator procedure covering both storage volumes and configuration.