·
2 min read
Why We Built a Draft → Publish Workflow
features
workflow
best-practices
Imagine editing a translation and it goes live immediately.
Now imagine you have 50 translations to update. Each one goes live the moment you save. Your users see half-finished work. Your CDN regenerates 50 times.
That's why we built the Draft → Publish workflow.
How It Works
Edit → Save (Draft) → Edit More → Save (Draft) → Review → Publish (Live)
- Save creates a draft version
- Drafts are NOT visible to your applications
- Make as many edits as you want
- Publish pushes all drafts live at once
Your users only see the finished work.
Benefits
Batch Your Edits
Update 50 translations throughout the day. Publish once at the end. One CDN regeneration, not 50.
Review Before Live
See all pending changes before publishing:
- What changed?
- Who changed it?
- When?
Catch mistakes before they reach users.
Version History
Every publish creates a version. Need to rollback?
- Open version history
- Find the good version
- Click Rollback
- New draft created with old values
- Review and publish
Your safety net.
Release Notes
When you publish, add a note:
"Fixed checkout button translations, added FAQ section"
Future you will thank present you.
The Workflow in Practice
Monday:
- Developer adds 20 new keys
- Translator updates 15 existing keys
- Content team fixes 5 typos
Tuesday:
- Everyone reviews the 40 pending changes
- Looks good
- Publish
One release, 40 changes, zero disruption.