Deployment checklist

Before deployment, run the build, validation, and size checks. Then manually inspect the home page, catalog index, one catalog detail page, one article, one guide, the search index, and legal pages. Use at least one mobile viewport and one desktop viewport.

Search the repository for old project names, old social handles, old route names, and placeholder dates. Check public/llms.txt, robots.txt, sitemap output, Open Graph metadata, and JSON-LD.

The template is intentionally strict because content sites often fail through small inconsistencies: a stale route in navigation, a schema ID pointing to the wrong page, or a placeholder fact that survives into production.

Adaptation Notes

Use this guide as a working pattern, not as fixed product copy. Replace the example nouns with your project’s real terminology, then verify that each internal link still points to a generated page. If a claim depends on external evidence, attach the source in the relevant content record instead of burying it only in prose. This keeps the guide readable for users and maintainable for editors.

Before publishing, inspect the rendered page on mobile and desktop. The template is intentionally dense, so headings, cards, tables, and callouts should be checked with real text rather than short placeholders. When a section no longer applies to your niche, remove it cleanly or replace it with a more useful workflow; do not leave empty headings behind.