Skip to content
NANATEC Delivery + Innovation
Search articles

Shipping a publishing workflow people trust

Product

Draft, review, schedule, publish. Every transition is an explicit command, and every change can be undone.

Wanjiru Mwangi

Engineering Manager

1 min read

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

  • #Architecture

Keep reading

All posts
Engineering

1 min read

A BFF in front of every frontend

Why our public blog and our dashboard never talk to the API directly — and what the extra hop buys us in security, caching and simplicity.

Amina Odhiambo

Engineering

1 min read

Autosave that never lies

Debounced, serialized and honest: how the editor decides when to say “Saved”, and what happens when two people edit at once.

Amina Odhiambo