Governance · 10 / 23
Publishing
The editor runs the server’s own publish checks, so an entry says what blocks it before anybody presses Publish.
Fields marked * are required before this entry can be published.
Required
Has an invalid format
How it works
- 01
Drafts save whenever you like, finished or not.
- 02
The Publish gate lists every field that would fail.
- 03
Fix a field and watch the gate flip to ready.
- States
- Draft, Published, Modified
- Checks
- The server’s own validation
- In bulk
- Only valid drafts publish
In depth · For editors, and whoever owns what goes live
The button never lies to you
The editor tells you what is missing while you write, because the check in front of you is the same validation the server runs on publish.
Four states, so nobody has to guess
- Not saved yet
A new entry. Nothing exists until you save.
- Draft
Saved, and never public.
- Modified
Was live and has unpublished edits. It is off the delivery API until somebody publishes again.
- Published
Live and current. What you see is what a reader gets.
The readiness check is the server’s check
A half-written draft always saves; "required" is enforced at publish time. The gate in the editor runs the same validation the server will, and a refused publish returns a per-field list of what to fix.
Under the hood
Status and the version timeline are written in one transaction, and a bulk publish re-validates every entry inside it, so only valid drafts go live.
Around the edges
- The button says what it does
- Save draft, Publish, Publish changes, or “Published · up to date” when there is nothing to do.
- Publishing is its own permission
- Somebody can be trusted to write without being trusted to make it live.
- Translations publish independently
- Each language has its own status, so German can be live while English is still being written.
- Shared fields ask first
- A save that would invalidate a published translation names the languages and fields before it happens.
Questions
Can I schedule a post for Tuesday at nine?
Not built in. Publishing happens when somebody presses the button or calls the endpoint; drive the endpoint from your own scheduler for a fixed hour.
Can I require somebody else to approve it?
Yes, per content type, with publication protection.
How do I roll back a bad publish?
Publish an earlier version from History. Unpublishing deletes nothing either.