Got the code? Welcome, builder!
You're heading into Invent the Future — instructors hand out the access code on day one.
You're heading into Invent the Future — instructors hand out the access code on day one.
Two weeks. One hackathon. One real audience.
Week 1 is the foundation: HTML, CSS, and JavaScript through hands-on sessions, then time on prompt engineering — how to get reliably useful results from an AI model. By the end of Friday you'll know enough to build something real.
Week 2 is the hackathon. You form a team, pick a social-impact problem, and spend four sprint days building a working web application before Day 10's presentation.
You start with nothing and end with a working web page. In the morning you'll learn how HTML gives content structure and CSS gives it style, then spend the afternoon building your own About Me page from scratch — no hand-holding. By the end of the day you have your first portfolio piece.
You make your page do things. JavaScript brings HTML to life — you'll learn to respond to button clicks, read what a user types, and update the page without reloading. Toward the end of the day you write your first AI prompts and find out what "zero-shot" means.
You move from "here's a prompt" to "here's a strategy." One-shot and few-shot prompting let you guide the model with examples instead of instructions alone. Then a crash course in visual design hands you the vocabulary professionals use — and a lab puts techniques and design specs directly in service of web features.
You complete the toolkit. Structured output gets the model to return data your code can use. Chain-of-thought reasoning walks it through problems step by step. Then you run all three major models side-by-side to see where they differ.
Skills week ends with a decision: what are you building, and who are you building it with? You'll form your team, choose your social-impact problem, lock in a project scope, and put your plan up for a gallery walk before Week 2 starts.
Week 2 is a four-day hackathon. Sprint 1 is about getting every section of your app into the HTML — structure, navigation, all of it named and in place. Nothing needs to look good yet; everything needs to exist.
The scaffold gets a skin. Today you write the real content and the CSS that turns your app from a default browser stylesheet into something that looks like a considered design.
Your app becomes interactive. You wire the JavaScript that makes it actually do something — form inputs, dynamic content, whatever user interactions your project needs. Mid-afternoon is a checkpoint demo so every team can see where the others stand.
Final build day. Morning is finishing what you started. Then you ship: every team deploys its project live on Netlify, and every camper deploys their own About Me page. Afternoon you stop building and start pitching — because a working product you can explain clearly beats a half-finished one you can't.
You present. Real audience, real feedback. Seven minutes per team: the problem, a live demo from your deployed URL, and what you learned building it. Then the closing ceremony.