Release Workflow
Domain Orchestration
How readable customer domains should align with preview state and release workflow.
Domain management is part of docs delivery, not a separate concern. If release state and DNS state drift apart, the platform becomes hard to trust.
Baseline expectations
- each site should have a readable default hostname
- preview URLs should stay distinct from production aliases
- production alias updates should follow promotion, not precede it
Domain lifecycle
| Stage | Domain expectation |
|---|---|
| Preview | Use preview URLs or preview-safe review paths |
| Ready for promotion | Domain intent is known, but production aliases stay unchanged |
| Production | Readable customer aliases update only after promotion succeeds |
Why this belongs in the docs product story
Readers do not separate domain behavior from docs quality. If documentation changes appear on the wrong hostname or a production alias points at the wrong release, the docs platform looks unreliable no matter how polished the theme is.
Readable domains are a trust feature
A memorable, predictable hostname is part of the product experience. It should feel as intentional as the docs shell itself.