Choose the evidence or recovery action that matches the current publishing boundary. A build, CMS edit, webhook, and public response can each report a different state.
Review these lessons
- Web publishing evidence: prove the build, deployment, and live route separately
- Headless CMS publishing: define which records become public routes
- CMS webhooks: handle duplicate, reordered, and missing publication events
- Published content caches: bound the stale window and purge the right key
- Preview and production publishing: keep content and configuration separate
- Web release rollback: check the page graph and preserve content state
Other checks
Common Mistakes
- Do not infer live content from an editor preview.
- Do not treat webhook delivery as page freshness.