Lesson 2.2 · 60 minSite structure and copy

What you will have

The student has docs/content.md: the list of pages and the full text of every section of the site, written from the brief, with every claim either true or replaced by a clearly marked placeholder for proof the student will supply.

Video

The video for this lesson is not recorded yet.

Prompts used in this lesson

Part 4 — Demonstration: sitemap and first draft

Purpose: Write all the text for our lead-generation site before any design, so
that later sessions can build pages straight from one file.

Context: Read @docs/brief.md. It is the only source of facts about the business.
The site has these pages: / (landing page), /thank-you, /privacy, /terms, and a
page-not-found page.

Done looks like: a file docs/content.md with
1. Sitemap: a table of each page, its address and the one thing it must achieve.
2. Site-wide text: header navigation labels, the main button label, footer text.
3. Landing page, section by section in this order: hero, problem, benefits,
   how it works, proof, FAQ, final call to action. For each section: heading,
   body text, button label if any.
4. Lead form: field labels, help text, error messages, the button label, the
   one-line note about how the data is used.
5. Thank-you page: full text, including what happens next and when.
6. Page not found: full text.
7. Privacy and terms: not the text, only a list of what each must cover and
   which business details I need to supply.
8. Page titles and descriptions for search results and link previews, one per page.
9. A final list of every placeholder in the file.

Constraints:
- Use only facts from the brief. Do not invent testimonials, customer names,
  numbers, ratings, prices, awards or guarantees.
- Where a fact or proof is missing, write a placeholder in exactly this form:
  [OWNER TO SUPPLY: what is needed]. Do not write example text in its place.
- The form asks only for name, email, phone and a message.
- Plain, concrete language. Short sentences. No superlatives.
- Before writing the file, show me the sitemap and the list of landing-page
  sections with a one-line summary of each, and wait for my approval.

In docs/content.md the benefits section says "[quote the invented claim]". That
is not in the brief. Find every statement in the file that is not supported by
docs/brief.md, list them, then replace each with a true statement from the brief
or an [OWNER TO SUPPLY: ...] placeholder.

Part 5 — Demonstration: variants, cutting, your own voice

Give me five alternative hero headlines and subheadings for docs/content.md.
Each takes a different angle: time saved, the same cleaner every visit, how
quickly we reply, the problem with unreliable cleaners, and a plain description
of the service. Use only facts from docs/brief.md. Do not change the file yet.

Here is how I actually write to customers: "[paste three or four of your own
sentences]". Rewrite the landing-page sections in docs/content.md to sound like
this person: same vocabulary, same sentence length, same level of formality.
Change wording only. Do not add or remove facts or placeholders.

Visitors will read this on a phone. Cut the landing-page text in docs/content.md
by about a third. Remove sentences that could appear on any cleaning company's
site. Keep every fact, every placeholder and every section. Then show me, section
by section, what you removed.

Read only docs/content.md, and nothing else in this project. From the landing
page text alone, answer in two sentences: what is being offered and to whom, and
what should the visitor do next? Then list anything that confused you.

Do along

Work on your own project. Pause the video where a step says so.

1. Open Claude Code in the project.
2. Pause when the main prompt appears in Part 4. Use it. Adapt the page list only if your site truly needs another page, and the form fields only if you cannot quote without one more answer; lesson 3.7 explains that every extra field costs conversions.
3. Approve or correct the outline, then let Claude write docs/content.md.
4. Pause at the end of Part 4. Run the honesty check: search for digits, "guarantee", "best", "trusted", "rated", "award". Trace each hit to your brief, or have Claude replace it with the correction prompt.
5. Pause after each prompt in Part 5. Ask for five headline variants; choose one and edit it in your own words.
6. Paste a few sentences of your own writing and run the voice prompt, then the cutting prompt.
7. Do the stranger test with a fresh session after /clear; if someone is nearby, ask them too. Fix what confused the reader.
8. Commit and push.

Check your work

1. docs/content.md starts with a sitemap table. → It lists /, /thank-you, /privacy, /terms and page not found, each with its purpose.
2. The landing page has hero, problem, benefits, how it works, proof, FAQ and final call to action, each with real text. → No filler text.
3. Search for OWNER TO SUPPLY. → Every hit names what is needed and appears in the list at the end.
4. Every number, promise and customer quote can be traced to docs/brief.md or to a real customer who gave permission. → Yes.
5. The button label is the same everywhere and matches the conversion action in the brief. → One label.
6. A reader unfamiliar with the business (a person, or a fresh session after /clear) reads the landing-page text. → They can say what is offered and what to do next.

Common problems

• A testimonial appears with a name and a city. → Claude followed the pattern of typical landing pages. → Use the correction prompt from Part 4; then add to CLAUDE.md: "Never invent testimonials, numbers or guarantees; use [OWNER TO SUPPLY: ...]."
• Placeholders contain example text ("e.g. 'Brightside changed my life'"). → The example will leak into the site later. → Say: "Remove example wording from every placeholder; keep only the description of what is needed."
• The copy sounds like every other site. → No voice sample was given. → Run the voice prompt with your own sentences, then the cutting prompt.
• The voice rewrite changed facts. → Constraint ignored. → Say: "List every fact you changed and restore the originals." Check with git diff, as in lesson 1.4.
• The FAQ answers questions nobody asks. → Claude guessed the objections. → Give it the real questions customers ask you, or mark [OWNER TO SUPPLY: questions customers actually ask].
• The stranger cannot say what to do next. → Several different button labels or a buried call to action. → Say: "Use one button label everywhere and state the next step in the hero and in the final section."

Homework

About 40 minutes, after the lesson. Nothing here is needed to start lesson 2.3. Keep the section names, the button label and the form fields as they are.

1. Two real readers (~15 min). Send the landing-page text to two people who do not know the business, ideally people like your audience. Ask: what is offered, what would you do next, and what would stop you? Write down their answers; fix what confused both. If the file changed, commit without a tag. Done when: you have two sets of answers, and both readers named the offer and the next step.
2. Start collecting proof (~15 min). Copy the placeholder list from the end of docs/content.md into your task list and give each item a date before lesson 3.5. Send the review-request message from the materials to three real customers. With the sample business, write the message but do not send it. Done when: every placeholder has a date and three requests are sent or drafted.
3. The questions customers really ask (~10 min). From memory and old messages, write down the five questions people ask before they buy. Compare them with the FAQ in docs/content.md. Have Claude replace guessed questions with yours, using only answers you give. Commit without a tag. Done when: every FAQ question is one a real customer asked, or is an [OWNER TO SUPPLY: ...] placeholder.

Save your work

git add -A
git commit -m "Lesson 2.2: site content"
git push