Put it on the internet (free), then decide what's next.

What "deploying" actually means

Right now your page lives in a folder only your computer can see. Deploying means putting a copy of that folder on a computer that's always on and open to the world, so any browser anywhere can load it. Companies exist that do this for free for small sites — genuinely free, not trial-free — because they make money on big customers and you cost them fractions of a penny.

We'll use two: GitHub (a home on the internet for project folders) and Vercel (a service that takes your GitHub folder and serves it to the world). Both free tiers, both used by professionals daily. This site — the one you're reading — deploys exactly this way. The whole pipeline:

Step 1 — two free accounts (10 minutes)

• github.com — sign up. Free tier.
• vercel.com — sign up, and choose "Continue with GitHub" when it asks. That handshake connects the two, which is the whole trick.

Step 2 — get your folder onto GitHub

If you did Lesson 6's homework, git is already set up and committed. Now, in your project folder, tell Claude Code:

It handles what it can and narrates the rest — including anything it needs you to click or sign into. This "walk me through it, do what you can yourself" phrasing is the power tool for any setup task from now on, way beyond this course.

When it's done, refresh your GitHub page — your project is sitting there with all its files. That's your folder, on the internet, with a home.

Step 3 — connect Vercel and ship

In Vercel: Add New → Project. It shows your GitHub projects; pick yours, click Deploy, change nothing. Watch it work for under a minute, and then it hands you a URL — something like my-page.vercel.app.

🎉 Congratulations!
Your project has been deployed.

[ Visit ]   my-page.vercel.app

Open it on your phone. Not your computer — your phone, over cell data, like a stranger would. That's your page, served from the actual internet.

Send the link to one person. This step is not optional and I'm not being cute: the moment someone replies "wait, you made this?" is the moment this stops being a course you took and becomes a thing you do.

You're done. Here's what you actually learned.

Seven lessons ago the terminal was scary. Since then you've briefed an AI agent, built a real page through conversation, corrected it when it drifted, recovered when it broke, and shipped it to a public URL. That loop — describe, build, look, fix, ship — is the entire craft. Everything I build for clients is that loop, run more times, pointed at bigger targets: dashboards, booking systems, automations, tools. None of it is a different skill. It's this skill, compounded.

The fork in the road

If you caught the bug: your second project is already waiting — Course 02: build your first game, where the game learns to display your real projects and you learn the skills this course didn't get to (data files, custom commands, project memory) — and Course 03 after it teaches your game to think, with the real Claude API. Or pick a small real annoyance in your life — a tracker, a calculator, a page for a friend — and run the loop again while it's fresh. When you're ready to see what bigger looks like, the tools I run my own business on are the kind of thing you can now grow into building yourself — and I'm packaging them up for people who'd rather grab them ready-made.

If you run a business and mostly learned "this is real, and I don't have the hours": that's a completely legitimate landing spot — you're now the rarest kind of client: one who can't be dazzled by jargon. When you want systems like this built and maintained for you, start with the free audit or just tell me about your week — first thing I'd automate, free, within 24 hours.

Either way: I told you at the start I wouldn't gatekeep this, and I meant it. Go build something.