Week 18: Create a Launch Checklist and Fix Bugs

This week in plain English

ObjectiveRun a proper pre-launch QA process and fix problems before final publishing.

Why this mattersReal websites need a launch process. Testing prevents embarrassing mistakes.

What she will makeA launch-ready version of one project plus a written QA checklist.

What “done” looks likeThe website passes link, mobile, calculator, SEO, sitemap and privacy checks.

At the end, she should be able to say:
“QA means checking a website carefully before launching it.”

Fortnight project: Commercial Project 9 completed.

Skills: QA, bug fixing, launch checklist, privacy check, sitemap QA, browser testing

Suggested session structure: 10 minutes objective, 10 minutes ChatGPT planning, 25 minutes building, 10 minutes testing, 5 minutes recap.

Commercial outcome

By the end of this week: One previous project should be cleaned up and ready to show as a polished sample.

Step-by-step

Create launch-checklist.html.
List every page in the project.
Click every link.
Test every form, calculator or quiz.
Resize browser to mobile width.
Check page titles and descriptions.
Check sitemap and robots files.
Fix issues and write down what changed.

Launch checklist table

Check	Status	Notes
All links work
Mobile layout works
Calculator/quiz works
Titles and descriptions exist
Sitemap is updated
No private information
Spelling checked

Bug fixing with ChatGPT

Prompt:
I will paste my HTML, CSS or JavaScript. Please help me find why it is not working. Explain the likely issue, show the corrected code, and explain the fix in simple words. Do not rewrite everything unless necessary.

Commercial quality checklist

A launch checklist page exists.
Issues found are written down.
At least three improvements are made.
Final project is tested online.