Operations · 21 July 2026 · 6 min read
Publication pipeline: draft, review, scheduled, published
How the lifecycle engine models editorial states, scheduled releases, per-locale translations and rollback without scattering status logic across the codebase.
Platform team · Content operations
One place for state
Allowed states and transitions live in a single lifecycle module. The admin UI, the REST transition endpoint and the scheduler all ask the same module, so an entry cannot reach a state that the pipeline does not recognise.
Scheduling and preview
Scheduled entries are promoted by a background pass, while preview tokens are bound to an environment and read-only. Production delivery therefore returns published rows only, and a preview link never widens access by accident.
Localised fields
Translations are stored per field and per locale with fallbacks, so a partially translated entry stays publishable and the delivery API can answer in the requested locale.