Next.js Client Launch Template

A lean starting point for client migrations, rebuilds, and new startup sites. The template reuses launch discipline—not a runtime page builder.

Start here

1. Work through the readable docs/launch/checklist.md. Its source and current state live in docs/launch/checklist.json.
2. Use docs/features.md during project kickoff. Default features are normal code: delete them when unused instead of adding flags.
3. For an existing site, begin with docs/launch/migration.md and docs/launch/url-map.csv.
4. Update a check with pnpm launch:checklist --set <ID> <todo|done|not_applicable>.
5. Add a client-specific check with pnpm launch:checklist --add-project <ID> <P0|P1|P2> <title> --detail <Markdown>.
6. Keep PLAN.md for the architecture audit and page-by-page roadmap.

Development

Requirements: Node.js 20.9+ and pnpm 10.

pnpm install
cp .env.example .env.local
pnpm dev

Quality checks:

pnpm launch:checklist
pnpm check
pnpm build
pnpm launch:audit --url http://localhost:3000 --mode template

Launch commands have separate jobs:

• pnpm launch:checklist displays manual progress and identifies automated items. Its --set, --add-project, --write, and --check options manage or validate the canonical checklist.
• pnpm launch:verify executes every named check whose checklist status is auto. It needs no running website and exits non-zero when a check fails.
• pnpm launch:audit runs those automated checks plus live crawling, route, metadata, indexability, sitemap, and production-safety checks against a URL.
• pnpm indexnow:key creates or rotates a site's IndexNow ownership key and root-level public verification file.

pnpm check includes pnpm launch:checklist --check so invalid checklist data or stale generated Markdown fails normal CI. It does not run pnpm launch:verify, because the base template intentionally contains marked placeholders until a client replaces them.

Before production, configure the real identity and run:

pnpm launch:verify
pnpm launch:audit --url https://example.com --mode production

pnpm launch:verify runs every checklist item whose status is auto; it exits non-zero while any named check fails. The production audit runs those functions alongside live route, metadata, indexability, and sitemap checks. It also fails while any manual P0 item remains todo.

Current implementation

• Phase 0 foundation: implemented.
• Phase 1 homepage: implemented with one /contact action, a stack trust bar, shared positioning sentence, reordered existing sections, FAQ, and close. Customer-proof sections stay omitted until real inputs exist; see docs/recipes/homepage.md.
• shadcn/ui: configured with the base-nova style; only the Button, Card, and Badge primitives used by current pages are checked in.
• PostHog: included through src/instrumentation-client.ts; add its token to activate it or delete the file and dependency.
• Privacy and terms: safe noindex scaffolds only. They deliberately block production until replaced and reviewed.
• Use cases and industries: /use-cases and /industries hubs, plus one detail page per JSON file in src/content/pages/{uses,industries}. Feature ids resolve through the shared visual resolver; see docs/recipes/use-cases.md.
• Visual workshop and launch assets: an exact server-only allow value exposes /dev, the full /dev/visuals inventory, and three template launch frames at /dev/launch-assets. pnpm launch:assets builds the production app and exports exact reduced-motion PNGs to artifacts/launch-assets; see docs/recipes/launch-assets.md.
• Blog: connected directly to Wisp with a configurable lead story, real-tag filters, compact search, numbered pagination, article contents/share links, related posts, RSS, and sitemap entries. Replace the demo publication ID or delete the blog for a client project.
• Contact: server-rendered page and form markup with bounded API validation, explicit SMTP delivery, minimized first/recent-touch attribution, basic abuse controls, optional Cloudflare Turnstile, and a clean removal path. Delivery stays unavailable until every server-only mail value is configured; Turnstile stays inactive until both of its keys are configured.
• llms.txt: a complete website-level example selling Launch Template, conditional homepage Link discovery header, focused source validator, production header/response/public-target audit, and configuration/removal recipe are included. Deleting public/llms.txt removes the discovery header rule on the next build or server start. pnpm launch:verify deliberately fails until the example is replaced for the client.
• Markdown representations: canonical page URLs return generated Markdown when an agent requests Accept: text/markdown, and /path.md returns the exact same representation for clients that cannot set headers. HTML remains the default on canonical URLs, quality values and HTTP 406 are handled, and optional files under can override individual paths. See .

Architecture rules

• Build explicit App Router pages.
• Keep page copy and composition in or beside the route.
• Promote a route-local component only after real reuse.
• Keep metadata and applicable structured data together in src/lib/seo.ts.
• Keep shadcn primitives in src/components/ui; add a component only when a current page uses it.
• Never introduce site.json, a marketing catch-all renderer, or a block registry.
• Do not ship plausible placeholder client details. Use loud sentinels that the audit can reject.

This is the beginning of the README. Read the rest at the original. Read the full README ↗