Ownership plus an audience. Students demo something real that they made and can show anyone.
Concepts
The brief
Take your club site and add one new capability you choose, or build a small new site using the same stack. It must be live (Vercel), store data (Supabase), and have one backend feature. Bonus for email or AI.
Ideas
- Events page with RSVP (new table + form + email).
- A guestbook or shout-out wall.
- A simple voting/poll feature for the club.
- A "merch interest" form that emails the organizer.
Talking points
- You now have every piece: page, database, backend, email, AI.
- Pick one thing that would make your site better and build it.
- Use Claude as your crew — but you direct, and you read the code.
- You'll demo it. Working and small beats fancy and broken.
Student activity (you do)
Workflow expectations
- Plan first in plain English (what's the feature, what data, what's the flow).
- Prompt Claude in steps; read and test each change.
- Commit often with clear messages.
- Keep secrets in
.env. Verify it deploys, not just runs locally.
Demo day (10 min each or gallery walk)
Each student shows: the live URL, the feature, and answers one question: "What's one line of code you understand and what does it do?" (Enforces the read-the-code habit one last time.)
Assessment
Use the rubric in Appendix E. Reward shipping, understanding, and good debugging over polish.
For the instructor
Let them struggle a little — productive struggle is where the learning sets. Your job shifts from teacher to consultant. Circulate, ask "what have you tried / what did the error say / what did Claude suggest?" before giving answers.