Delivery
The preview-safe path from a content change to a trusted production deployment.
The delivery section is where DevDocs stops being a theme demo and becomes a product. This is the workflow layer around the docs shell: previews, verification, domain readiness, and promotion confidence.
Delivery outcomes
Preview Environments
What a reviewable preview must expose before humans rely on it.
Release Proof
How the local and live proof loops establish trust before merge and after deploy.
Domain Orchestration
How readable production aliases should stay aligned with release workflow.
Delivery principles
- previews should be easy to review and hard to misuse
- production promotion should require evidence, not hope
- domain updates should stay attached to release state, not ad hoc manual steps
- the docs surface should expose enough context that reviewers can catch UX drift quickly
The proof loop in practice
Build a preview-safe candidate
The preview environment should expose root docs, diagnostics routes, and any bypass hooks needed for automated review.
Run a review battery
Reviewer heuristics, browser checks, and Playwright verification should all agree that the preview behaves like a credible public docs surface.
Promote only after evidence is in hand
Local checks, preview proof, and post-merge production verification should line up before we call the change complete.