Lock it down and the pre-launch checklist
Add the last Module 10 protections to your client site (security headers, Dependabot, a secrets check and a backup), pass SECURITY-CHECKLIST.md with proof, then create and pass a new PRE-LAUNCH-CHECKLIST.md that checks everything a client would notice: content, phones, speed, search basics, accessibility, forms, emails and the admin, on the live site.
Why this matters
You've built a client site in eight lessons. It works. But "it works on my phone" isn't how professionals launch, and it isn't what a client is paying for. They're paying for nothing going wrong after you leave.
Two checklists do that job:
SECURITY-CHECKLIST.md(from Lesson 10.9): keys, database, forms, login, headers, updates, backups. It protects the business's customers and reputation.PRE-LAUNCH-CHECKLIST.md(new today): everything the owner and their customers will notice. A wrong price, a button too small to tap, a page that takes eight seconds on mobile data, a form a screen reader can't use, an email that looks broken on a phone.
Every line gets proof: something you saw, ran or measured, today. Not "I'm fairly sure". And the blank copies go into your templates folder, so every client site from now on gets the same treatment. In Module 12, LAUNCH-CHECKLIST.md picks up where these leave off, with everything to do with the domain.
In the full lesson
- The idea in plain English
- Do it
- Check it worked
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.