Content Workflow

Luna separates workflow state, saved edit state, and the live release. Use Private while work is not ready, inspect the authenticated draft, and publish only the page or coordinated site scope that has passed review.


Read the current workflow state


Open the workflow control and inspect the Public or Private label before changing anything. In the visible Public state, the popover explains live visibility and exposes Make Private as a separate action; viewing the control alone changes nothing.

Luna Public workflow popover explaining live visibility and showing the Make Private action
The Public popover identifies live visibility and the separate Make Private boundary.


Public and Private describe release eligibility


Private content remains available to permitted editors in the edit tenant and is not intentionally exposed as a public page. Public content has a live release, but later saved edits still remain draft changes until they are published again. Save never means publish.


Edit state versus live state


The edit domain can show the latest saved revision while the live domain continues to show the last published release. Always compare the exact path and domain when reviewing a change.


Use a safe review sequence


Confirm the page and path. Finish copy and media. Check heading order, links, forms, metadata, alt text, and navigation placement. Inspect Desktop, Tablet, and Mobile Views. Coordinate any page lock handoff. Then choose the smallest correct release scope.


Coordinate a full-site release


Use the pre-publish check when several pages or global surfaces must move together. Inspect the changed-surface summary, edit and live domains, Private-page warning, and required confirmation before proceeding.

Luna pre-publish check with changed surfaces, edit and live domains, Private-page warning, and disabled Publish action
The pre-publish check defines the coordinated release boundary before confirmation.


Choose page or site scope


Publish one page for an isolated content change. Choose a complete-site release when the change depends on multiple pages, the navigation hierarchy, theme colors, fonts, presets, the global Navbar, or the global Footer. Review Private content so it is not mistaken for part of the public release.


Keep review and release ownership explicit


Assign one person to perform the final cross-surface review and one authorized release owner. Other editors can prepare drafts, but save ownership, lock handoff, and publish ownership are different responsibilities.


Workflow checklist


Correct path and state. Latest edit View reviewed. Live state identified. Locks coordinated. Desktop, Tablet, and Mobile checked. Links and interactions tested. Page versus site scope chosen. Live domain verified after any future publication.


Next steps


Read Multi-User Editing for handoff semantics, Private & Published for the state boundary, and Publish a Site for the complete pre-publish and post-release sequence.

Questions, ideas, or bugs?

Explore what we’re building next, ask the Luna team for help, or send a focused bug report.