Saving is progress. Publishing is a decision.

A website is rarely finished when it first goes live. Headlines improve, details change and the next story is always taking shape. The challenge is to make that work possible without exposing every unfinished edit to readers.

Give the draft its own place

GroCMS keeps a working revision separate from the published revision. Saving records the work. Publishing chooses the version that the public website should show.

That distinction is useful even for a team of one. You can revise a page, look at a private preview and decide whether it is ready before changing what visitors see.

Review a specific version

A review should refer to the work someone actually submitted. In GroCMS, a review is tied to a saved revision. Later edits do not silently change the version under discussion.

This gives the author and reviewer a concrete point of reference. The team can inspect the selected revision and make the publication decision with that context.

Schedule with the same clarity

A scheduled action also selects a saved revision. The background worker processes the action when it becomes due. If the working draft changes in the meantime, it does not replace the scheduled version.

The operating setup still matters: the worker must be running and the installation must be maintained. An editorial feature and an operational responsibility can both be true.

A habit worth keeping

Save the work as it develops. Preview the version you intend to share. Use review where it helps. Then publish deliberately.

For the details, read How GroCMS works and the publishing schedule guide.