Lesson 3.8 · 45 minSupporting pages

Purpose: add the thank-you page and send successful form submissions to it.

Context: LeadForm currently replaces itself with a success message. Copy for
the page is in docs/content.md (add it to the content folder). Route:
/thank-you.

Done when:
- app/thank-you/page.tsx shows a confirmation heading (h1), what happens next,
  the phone number from content/site.ts for urgent requests, and a link home;
- after a successful submission LeadForm navigates to /thank-you; the sending
  and error states are unchanged;
- the page's metadata asks search engines not to index it, and nothing on the
  site links to it.

Constraints: existing components and theme tokens; text from the content
folder. Read the redirecting and metadata guides in
node_modules/next/dist/docs first. Before reporting: build and lint; in the
browser submit valid data and confirm the address becomes /thank-you; submit
with error@example.com and confirm the form shows its error state; show me
the robots meta tag from the page's HTML.

Purpose: add first drafts of the privacy policy and terms pages.

Context: the site collects name, email, phone and message through the lead
form (see components/LeadForm.tsx and docs/architecture.md). Today the only
third party processing data is the hosting provider, Vercel; database, email,
analytics and advertising services come later and are NOT in use yet.
Business details: [legal name, address, contact email, phone, country].

Done when:
- app/privacy/page.tsx and app/terms/page.tsx exist, each with an h1, a "last
  updated" date and plain-language sections under h2 headings;
- privacy covers: who we are and contact; what data we collect; why; who
  receives it; how long we keep it; people's rights and how to use them;
- terms cover: what the site offers; that a quote request is not a contract;
  acceptable use; liability; governing law; contact;
- both are linked from the footer, and the form's privacy link works;
- docs/legal-review.md lists every statement you assumed or were unsure of,
  as a checklist for me and a legal reviewer.

Constraints: describe only what the site does today; no cookies, analytics or
advertising tools that are not installed. Do not invent retention periods,
registration numbers or legal claims; where a fact is missing write
[TO CONFIRM: …] and add it to the checklist.  Before reporting: build and lint, open both pages, and
list every [TO CONFIRM] you left.

Purpose: replace the default "not found" page with our own.

Context: Next.js App Router; read the not-found file convention in
node_modules/next/dist/docs.

Done when: any address that matches no page shows a friendly h1, one
sentence, a primary button to / and a link to /#quote, in our design, inside
the normal header and footer; the response status is still 404.

Constraints: existing components and tokens; text in the content folder; not
the experimental global not-found feature. Before reporting: build, start the
production server, request a made-up address, and report the HTTP status code
and a screenshot.

Purpose: give the site its identity in browser tabs, search results and
shared links.

Context: the live address is https://[your-domain]. Business name and offer
are in docs/brief.md; page copy in docs/content.md. The scaffold's favicon
and default metadata are still in place. Read the metadata, app-icons and
opengraph-image pages in node_modules/next/dist/docs first.

Done when:
- content/site.ts has siteUrl set to the live address and the root layout
  uses it as the metadata base;
- every page has a unique title, "Page name | Business name" (the home page
  uses the main offer plus the business name), and a unique description of
  one or two honest sentences, kept in the content folder; show them to me
  for approval;
- the favicon and icon files in app/ are our own mark, made from the logo or,
  without one, the business initial on the brand colour;
- a 1200×630 link-preview image with the business name and offer in our
  design sits in app/ under the Next.js file convention, with alternative
  text; Open Graph title and description are set;

Constraints: no claims that are not in docs/content.md. Before reporting:
build; start the production server; for /, /privacy, /terms and /thank-you
give me a table of title, description, robots value and preview-image
address taken from the rendered HTML, not from the source code.