Production acceptance checklist

Run this checklist in a real browser after production deployment. A successful build is not sufficient evidence.

Main journeys

• The home page loads on the canonical HTTPS domain.
• The primary documentation journey reaches installation and quick start.
• Search finds a known page and opens the correct result.
• Desktop navigation works.
• Mobile navigation works at a narrow viewport.
• Locale switching works where the site supports more than one locale.

Metadata and discovery

• The canonical URL matches the current page.
• Open Graph and social metadata use the correct product identity.
• /sitemap.xml and /robots.txt load and reference the canonical domain.
• Public assets, icons, and social images load.

Analytics and feedback

• The page loads exactly one correct Plausible script.
• The browser sends a pageview without an error.
• “Was this page helpful?” records a docs-feedback event.
• The feedback issue link opens the correct repository and template.

Trust links and runtime

• GitHub, Discord, legal notice, and privacy links work.
• The browser console has no hydration or runtime error.
• The network log has no failed required request.
• No asset or internal link is broken.
• Production is public, not a protected preview or stale deployment.

A 522 response, protected preview, stale domain, failed main story, or missing package build blocks acceptance.