Course Lesson 10 of 11
Developer handoff
Course progress 0 of 11 complete
Responsive checks proved the pages. Handoff proves another person can continue without reading your chat history. Vibe coding still needs a person who can read applies when you are the reader of your own folder.
What goes in the zip
Section titled “What goes in the zip”index.html,services.html,contact.htmlstyles.cssnotes.md(brief, sitemap, colours, responsive checks)- any images you actually use, with credits if required
README.md(new)
Leave out: chat exports, node_modules, private phone dumps, .env files, and half-finished experiments in other folders.
README skeleton
Section titled “README skeleton”# Common Ground Workshop
## Open locallyOpen index.html in a browser. No build step.
## Decided- Audience: …- Pages: Home, Services, Contact- Colours: ink … paper … accent …- Tone: plain and welcoming
## Open questions- Final phone number / email to publish- Whether a map embed is wanted later- Hosting preference
## Out of scope for v1- Payments, login, blogFill the blanks from notes.md. Do not invent answers to look finished.
Talking to a builder
Section titled “Talking to a builder”You can ask an assistant to draft the README after your facts exist. You still delete anything you cannot stand behind. The builder should be able to open index.html cold and see the same site you tested.
- Create
README.mdwith the skeleton above and your real decisions. - Confirm the zip (or folder) contains only what a stranger needs.
- Open the folder on a second machine or user profile if you can; otherwise open the HTML via a fresh browser profile.
- Ask a friend—or yourself tomorrow—to find the accent colour from the README alone.
- Fix anything that required tribal knowledge from the chat.
Before you continue
You are ready for the Capstone when:
- README lists decided facts and open questions separately
- the folder opens without a build step
- chat history is not required to understand the site
Mark this lesson complete when those three are true.