Join the class board.
Add your links when ready.
Share your project, explore your classmates’ work, and star each other on GitHub.
Scan to join · no sign-in
Build a business people can use · four-week assignment
Working version: Thursday 19 November 2026. Improved version: Thursday 26 November 2026. Turn your deployed site into a useful customer journey. Apply the course skills, show what actually works, and explain what you learned.
Week 1 · Offer & CTA
Choose one customer and problem. Make your offer clear, add a primary CTA and publish the site. Record your starting point.
Week 2 · Make the journey work
Implement the action your business needs: buy, book, enquire or register. Connect storage and email where needed. Test the full journey, including confirmation.
Week 3 · Test & measure
Run three user tests or customer conversations. Check mobile and keyboard use. Verify an analytics event, fix one issue and record before/after evidence.
Week 4 · Launch & show evidence
Create one content asset with a CTA, run a small distribution experiment and prepare a three-minute demo. Explain your agent workflow and next improvement.
Bring on 19 November
- Your live website and GitHub repository, with meaningful commits showing progress.
- One complete customer journey. Use test mode for payments; show confirmation and any relevant saved record or email.
- Evidence from three user tests or conversations, one verified analytics event and one improvement based on feedback.
- One content asset and distribution experiment, plus the agent tasks, handoffs and corrections behind your work.
- An evidence record in
docs/assignment-evidence.md. Explain anything incomplete or not relevant to your business.
For 26 November: act on the feedback from the 19th, demonstrate the improved journey and show the commits and test results behind the change.
Optional extensions: booking reminders, a useful AI feature, NFC access, a lead magnet, automation, session replay or another feature that solves a real customer problem. Explain its value and show a test. You do not need every tool or all 18 signals.
How review works: the dashboard finds code and documentation signals. These are evidence to inspect, not proof that a feature works or an automatic grade. We review usefulness, working behaviour, testing, learning and your ability to explain the work. Missing signals are not automatic failures.
Download assignment textDownload evidence templateDownload agent review promptQuests: 100 core points + 20 bonus. Expand your project to submit evidence from the browser you registered with. Instructor: sign in at the course hub, then .
What we’re shipping
Loading projects…
Open a classmate’s website, test one customer action, then visit their repo to leave a star. Course evidence checks look for 18 implementation and documentation signals in public repositories. ✓ means evidence found, not a passed requirement. Open “Course evidence” for evidence. Latest commits are checked periodically; GitHub may limit checks.
Course evidence: ✓ code or documentation found · ○ pending, unknown or not detected. Evidence does not confirm a working feature or set your grade. Expand a card’s checks for evidence and the live test to perform.
Project updates
Checking public GitHub activity…