CMS publishing and recovery

Purpose, scope, and required role

Use the authorized admin CMS for public-page content, including schedule and gallery management. This does not approve messaging, image rights, or an emergency database change. Saving a draft is not publishing.

Supported workflow

The Public Pages area shows the selected route, last publish time, Save Draft, Publish, validation state, and Revision History. Draft changes remain separate from the currently published page until an authorized publish action succeeds.

1. Confirm the page, approval, final copy, links, image description, rights, and timing.
2. Select the page and edit only required fields. Resolve inline validation before saving.
3. Choose Save Draft and reopen/preview it to confirm values persisted without adjacent changes.
4. Obtain editorial approval, choose Publish once, and record page, revision/time, and approver.
5. Verify the public route in a clean/non-admin session, including responsive presentation where relevant.

Failure, rollback, and evidence

Unsaved-change indicators, validation failures, and publish errors are stop conditions: retain the error and do not retry blindly. For a bad publish, use Revision History restore when available and verify the public result; source notes restoring must refresh the form state before another publish. If no safe revision exists, escalate—never edit production tables directly. A toast proves a UI action only; report CMS publish, deployment, and public observation separately.