Serve It

Everything you've built for five lessons lives in a kitchen with no door. Your page works — but only on the machine that cooked it. If this course has one moment we've been walking toward, it's the next fifteen minutes: your page, at a real address, on the open internet, opened on your phone.

We keep saying "wow point" about this step because we lived it — the feeling of your creation loading on a device that has nothing to do with your setup is categorically different from "it works locally." It's the day builder stops being aspirational vocabulary. (The full story and alternatives live in this recipe — today is the course version, tuned for your exact project.)

What you'll plate today

https://your-chosen-name.pages.dev — live, free, yours. Plus the ritual that makes it count.

Ingredients

Your first-kitchen folder — page in the shape you're proud of
A free Cloudflare account: dash.cloudflare.com — email only, no credit card, two minutes. Make it now, then come back.
About 15 minutes

Cook

1. The pre-flight taste

Your page is about to become public. One order first:

Read index.html as a stranger would. Is there anything on this page
I might not want public — full real name, phone, email, workplace,
anything? List what you find; change nothing yet.

Decide like an adult who owns the page: alias or name, keep or cut. (Changing later is one sentence and a re-deploy — this isn't a tattoo.)

2. Ship it

Put this page on the real internet, for free.

1. Confirm this project is just static files a browser can open,
   with no secrets in them.
2. I have a free Cloudflare account. Deploy with Cloudflare Pages
   under the project name [PICK-A-NAME] — it becomes my URL,
   [PICK-A-NAME].pages.dev, so pick me a backup name too in case
   it's taken.
3. A browser window will pop up for a one-time Cloudflare login —
   tell me when to expect it, then wait for me.
4. When it's live, give me the URL and verify it actually loads.
5. Make a save point: "first deploy".

The scariest thing that happens is step 3 — and it's a login button. Click approve. Watch the terminal do in seconds what used to take a sysadmin an afternoon.

3. The ritual (do not skip)

Open the URL on your phone. Not the laptop — the phone. The phone is the proof, because it never touched your kitchen.
Send the link to exactly one person who'd enjoy it. Watch the "wait, YOU made this?" come back. That message is the actual graduation certificate of this lesson.

4. Learn the update move

Change one small thing on the page, then:

Ship the new version.

Same URL, new dish, seconds. This is the loop you'll live in from now on: cook locally, taste, ship.

When it burns

Project name taken — first come, first served across all of Pages. Use your backup name or get creative; you'll say this URL out loud someday, pick one you like.
No login window appeared — the terminal prints a login link instead. Ask: "show me the login URL" and click it yourself.
URL shows "nothing is here yet" — freshly deployed sites can take a minute to wake up worldwide. Sixty seconds, refresh, it appears.
You spot your address/phone/full name after going live — no panic: edit, "ship the new version", gone. (Caches can hold the old page a few minutes.)
It suggests connecting GitHub — a fine grown-up workflow, not today's dish. "Direct deploy only for now."

Order up

□ Your page loads at your-name.pages.dev — on your phone
□ One person who isn't you has opened it
□ You shipped an update with one sentence
□ Save point "first deploy" exists

Take a second with this: five lessons ago you had never told a computer what to build. Now something you made has an address on the internet. The remaining lessons are about what a person with that ability does next — starting with pointing it at your own real life.

Next up — Lesson 07: Cook Your Own Data. Your files, your spreadsheets, your mess — turned into answers by the same loop.

Stuck on a step? Question box below — deployment has the most moving parts so far, and questions here improve the lesson for the next cook.