Drafts, then live
Every change lands in a draft layer first. Going live is a separate, deliberate step, guarded by a check on the site as it would become. It is the one lifecycle in the engine.
The choice
Content systems grow overlapping notions of visibility: a draft flag, a scheduled state, a preview mode, a staging environment for templates. Each is a separate mechanism with its own bugs, and they interact badly.
CTXR has one: two layers, draft and live, for everything — content, templates and files alike. Preview is the whole site seen through the draft layer. There is no third state. The mechanics are on Drafts and going live.
What it buys
Delegation without fear. A key that may write but not publish can do real work and no harm, because nothing it does reaches a visitor. See Who can do what.
A check with teeth. Because publishing is a distinct moment, the site judges the result before it exists: the live site plus this draft. A draft that would break the site does not go live; a take-back that would leave broken links is refused. Nobody skips the check.
Templates included. A designer’s new shell is a draft like any content change, previewed on the real site and refused if it does not parse. The draft layer is staging.
Indexes included. The engine keeps one index per root of what lies on disk, and the draft layer gets the same index beside it — small, the round’s own rows, gone when the round closes. A preview reads live ⊕ draft from those two, so a staged page is in the register and in the search the moment it is staged, at the same cost as live — in the place publish will give it, and a staged file that decodes to nothing is gone, as its page is; the public projections and the visitors’ search read live alone.
Reversibility until the last step. Something wrong on the live site goes back to draft, to be fixed or dropped. Removal for good is two steps, and the file is still in history after both.
What it costs
A shared draft layer, not a private one. A colleague with the right to publish may publish your draft. CTXR chose collaboration over exclusion on purpose, and the check on publishing makes that safe. Someone who wants a private workspace has history to fall back on, not a personal sandbox.
The principle it expresses
Visibility is one mechanism, and every other feature rides on it. Should CTXR ever carry content only some people may see, that would be the same layer machinery with a different test — not a new flag. One mechanism understood completely beats five understood roughly.