Shipping a publishing workflow people trust
Draft, review, schedule, publish. Every transition is an explicit command, and every change can be undone.
Wanjiru Mwangi
Engineering Manager
1 min read
On this page
Editors told us the same thing in every interview: they need to know what will happen when they press a button, and they need a way back.
No generic “set status”
The article has explicit operations — submitForReview, approve, schedule, publishNow — and each one checks who you are and where the article is in its life.
Scheduled means durable
A scheduled article is a database record, not a timer. The worker claims due jobs safely and calls the very same publish command a person would.
Manual and scheduled publishing share one path
Duplicate delivery never publishes twice
Overdue jobs are visible, not silent