ASSIGNMENT: BUILD A BUSINESS PEOPLE CAN USE Working version: Thursday 19 November 2026 Improved version: Thursday 26 November 2026 Over the next four weeks, turn your deployed website into a useful customer journey. Build on the course work and show what you can implement, test and explain. Week 1 — Offer and CTA: choose a customer and problem, clarify your offer, publish your site and add one primary action. Week 2 — Customer journey: make buying, booking, enquiring or registering work from start to confirmation. Add storage and email where relevant. Use test mode for payment demonstrations. Week 3 — Test and measure: complete three user tests or customer conversations, test mobile and keyboard use, verify an analytics event and fix one issue. Week 4 — Launch and evidence: create one content asset with a CTA, run a small distribution experiment and prepare a three-minute demo. FOR 19 NOVEMBER Submit your live website and GitHub repository on the business dashboard. Add docs/assignment-evidence.md to the repository with: - Your customer, problem, offer and CTA. - A demonstration of one working customer journey and its test results. - Three anonymised user tests or customer conversations and the changes they informed. - Evidence that one useful analytics event works. - One content asset, your distribution experiment and honest observations. - Your agent roles, task boundaries, handoffs, reviewed commits and one correction you made. - What remains incomplete, what is not relevant and your next improvement. Bring a three-minute demonstration: customer/problem, working journey, evidence, lessons and next step. Keep meaningful commits throughout the month. Do not include credentials, customer personal data or payment details in public evidence. FOR 26 NOVEMBER Use the feedback from 19 November to improve your project. Demonstrate the updated journey, relevant commits and test results. Explain what changed and why. OPTIONAL EXTENSIONS Add something useful beyond the core: booking reminders, an AI feature, NFC access, a lead magnet, automation or another improvement. Explain the customer value and demonstrate a test. You do not need every platform or all 18 dashboard signals; justify features that are not relevant to your business. REVIEW We review customer value, working behaviour, testing evidence, iteration and your ability to explain the work. The dashboard finds code and documentation signals; it does not automatically verify functionality or assign a grade. Real learning matters more than tool count or commit count. Report failures and limitations honestly. Dashboard: https://connectea-course-hub.vercel.app/board Submit project: https://connectea-course-hub.vercel.app/join QUEST POINTS Complete the quests inside your dashboard entry. Core: publish 10; offer and CTA 10; usable design 10; customer journey 20; testing and fixes 10; feedback from three people 10; analytics 5; agent workflow 10; launch experiment 10; follow-up improvement 5. Total: 100 core points. Optional: useful extra feature 10; useful automation 10. Up to 20 bonus points. Submit public evidence from the browser you registered with. Your instructor reviews it before points are awarded. Detected code alone earns no completion points. Quest points show progress and are not an official course grade.