Does saving a CMS edit publish it to the live website?

Saving an edit should make it available for review without immediately changing the live website. For Maetree’s own website, we chose a workflow in which a CMS save goes to GitHub, Cloudflare builds staging automatically, and production waits for approval of a specific revision.

This answers a practical question from our website planning: what happens when someone saves a page while it is still being written?

A save and a release are different steps

Our CMS stores page and article content in the website repository. Saving creates a recorded change. A successful staging build then gives the team a working page to inspect, including its links, layout and contact details.

The production build prepares a separate version. It does not automatically activate it. The person approving the release reviews the identified staging revision, and the maintainer publishes the matching production version. A later save needs its own review.

Keeping the revision matters. An approval of yesterday’s page should not accidentally publish today’s unfinished changes.

What the editor checks

Before requesting publication, the editor reads the page as a visitor would. Does the opening answer the reader’s question? Are names, dates and contact details correct? Do links work? Is the page readable on a phone?

New articles also have a readiness setting. Leaving an article unpublished keeps it out of the public build. That setting helps with drafts, but it does not replace review of edits to an already published page.

The limit of our current arrangement

We chose one editor at a time for the first version of this workflow. That keeps day-to-day publishing simple. It also means the team must finish or clearly pause one set of edits before another person starts. Separate working branches and independent approvals are a later improvement.

This is an operating process, so it depends on the team following it. Account administrators still have their normal publishing powers.

What we take from this project

A useful CMS needs a clear answer to three questions: where is the saved work, who reviews it, and which revision becomes public? We made those steps explicit for our own website rather than treating the Save button as a release decision.

Read how we separate website hosting from other services or contact Maetree about your next product release.