Make the game public and prepare the demo. Shipping means it runs outside your computer.
Right now your game exists on your computer. After today, it exists on the internet. Anyone with a link can play it. This is the moment every developer remembers — the first time their work goes live.
Video: Git Explained in 100 Seconds (2 min)
Quick refresher on Git — the version control system that powers GitHub Pages, the platform we'll use to put your game online for free. Understanding the basics of push, commit, and deploy is all you need.
Discussion after watching: What does it mean to "deploy" something? How is putting code on the internet different from having it on your computer? What could go wrong when a local file goes live?
A game isn't shipped until someone else can play it. Today we put the game online and prepare a 3-minute demo. Both games are client-side only, no backend, static files — perfect for free static hosting.
All of these work with static HTML/CSS/JS:
- GitHub Pages — free, easy, integrates with version control
- Cloudflare Pages — free, fast global CDN
- Netlify — free, simple drag-and-drop deployment
Each child prepares a 3-minute presentation covering:
- What is the core loop? — explain the fundamental cycle
- Where is the risk? — what creates tension
- How does progression work? — how does the player advance
- What is the signature feature? — what makes your game unique
- Live demo of one full cycle — show it working
You need: Paper, a pencil, and a timer.
Write a 3-minute demo script covering these 5 beats:
- What is your game? (15 seconds) — One sentence. "My game is called ___ and it's about ___."
- Show the core loop. (45 seconds) — Play one full cycle: action → reward → decision.
- Show the risk moment. (30 seconds) — Get into danger. Show what happens when the stakes are high.
- Show the signature feature. (30 seconds) — The one thing that makes YOUR game unique.
- What would you add in V2? (30 seconds) — One or two ideas for the future. This shows you're thinking ahead.
Now practice:
- Set a timer for 3 minutes.
- Read your script out loud while playing the game.
- Did you go over time? Cut something. Under time? Slow down and show more.
- Practice it one more time. It will feel better the second time.
Pro tip: The best demos look effortless because they were practiced. Stumbling is fine during practice — that's what practice is for. Tomorrow is the real thing.
Game loads from a live URL. Demo script is written and practiced once.
No last-minute features. If something is broken on the live version, fix the deployment — not the game.
File path errors (relative vs absolute paths) — use relative paths consistently. A path that works locally may break on a server.
Forgetting to upload all files — check that every CSS, JS, and asset file is included in the deployment.
Testing only on localhost — the live version is the real test. Open it in a fresh browser with no cache.
Not practicing the demo out loud — a demo you've never spoken is a demo that will stumble. Practice once, minimum.
The live URL moment is magical. When they see their game at a real web address for the first time, pause and let it sink in. Let them share the link with someone — a friend, a grandparent, a cousin. That's shipping.
Deployment may have hiccups. File paths that worked locally may break on a server. Images may not load. This is normal and educational. Walk through errors together — this is real deployment debugging.
The demo script teaches communication. Explaining your work clearly is a skill as important as building it. If they struggle to describe their game, help them find the right words. "What does your game DO?" is a great starting question.
Film the practice if possible. Watching yourself present is uncomfortable but incredibly useful. They don't have to share the video — it's just for self-improvement.
Tomorrow is LAUNCH DAY. You present your game to the world. The code is frozen. The site is live. Tomorrow you stand up, show what you built, and celebrate shipping. This is it.