If you've followed along since Module 0, stop and notice something: you now have a live website. It's yours. It runs on a server you set up with your own hands, it's locked down with a real firewall, it renews its own HTTPS certificate, it restarts itself if it crashes, and it's backed up. Most people who use the internet every single day have never done any of that. You have.
Consolidate everything and point toward what's next.
The capstone challenge
Every module in this course has been building toward one moment: shipping something that's entirely yours, start to finish, with nobody holding your hand. That's the capstone challenge. It isn't a quiz or a graded assignment — it's just you, using every skill you now have, on a project you actually care about.
Pick something small. Small isn't a compromise here — it's the whole strategy. A tiny project you actually finish and launch teaches you more than a huge one you never ship. A link-in-bio page, a personal blog, a little tool that does one useful thing, a small game — anything you'd be a little proud to text a friend. The steps below are the exact same ones you already used in Modules 6 through 9, just done once more, on your own, without a module walking you through each click.
-
Pick your project
Something small and personally meaningful. You'll actually finish it, and that's the whole point.
-
Build it with Claude
(Modules 6–7) Describe what you want in plain English and build it together, one step at a time.
-
Run it on your server
(Module 7) Get the app started and keeping itself up on your VPS, the same way you did with your first project.
-
Point a domain at it
(Module 8) Buy or reuse a domain name and aim its DNS at your server's IP address.
-
Get HTTPS
(Module 8) Let Caddy fetch a free certificate automatically, so visitors see the little padlock.
-
Set it to auto-restart
(Module 9) Hand the app to pm2 so a crash or a server reboot doesn't take your project down for good.
-
Take a snapshot
(Module 9) Back up the whole server once your project is live, so today's work is never at risk.
Your capstone checklist
Build with Claude → run it on the server → point a domain at it → get HTTPS → set it to auto-restart → take a snapshot. Six moves, one finished project. Check them off one at a time and you'll have shipped something real, by yourself, on infrastructure you understand.
Where to go next
This course covered the essentials — enough to build, launch, and maintain a real site on your own server. There's more out there, and now that you understand the fundamentals, the more advanced tools will make a lot more sense than they would have on day one. Here's what people usually reach for next.
Databases
A place to store information that sticks around between visits — user accounts, blog posts, scores. Think of a database as a filing cabinet for your app: everything has a folder, and you can find it again instantly.
Environment variables & secrets
Passwords and API keys shouldn't live inside your code — if you ever share that code, you'd be sharing the keys too. Environment variables, usually kept in a `.env` file, keep secrets safely separate.
CI/CD
CI/CD is a robot assistant that ships your updates for you — push your code, and it tests and deploys itself, no manual steps required.
Multiple projects, one server
A single VPS can run several apps side by side. Caddy, the tool you already set up in Module 8, can route each domain — or subdomain — to a different app running on the same machine.
When to use managed platforms
Sometimes a hands-off host like Netlify, Vercel, Railway, or Fly.io is genuinely the smarter tool for the job. You now understand what's happening under the hood, so you can choose them on purpose instead of out of necessity.
Quick troubleshooting reference
Things will occasionally go sideways — that's normal, even for experienced developers, and it will keep happening long after this course ends. What changes with experience isn't fewer problems, it's a faster, calmer process for finding the cause. Here's your first-response checklist before you panic.
When something's not working
- Can't connect at all? Double-check the server's IP address and that you're using the right SSH key.
- Site won't load in the browser? Check three things in order: is the app running (
pm2 status), is the web server healthy (systemctl status caddy), and are ports 80/443 open (ufw status). - Domain not working yet? DNS changes take a little while to spread across the internet — wait a bit and check again.
- Something broke and you don't know why? Read the logs — they usually say exactly what went wrong (
pm2 logs). - Don't recognize a word in an error message? Look it up in the glossary — every term in this course is explained there in plain English.
Where to keep learning
The best way to keep learning is the same way you got here: build the next small thing. But when you want to go deeper on a specific tool, these are worth bookmarking.
- docs.claude.com — the official documentation for Claude Code, straight from the source.
- Your hosting provider's tutorials — DigitalOcean's Community tutorials, for example, are beginner-friendly and cover almost every server topic imaginable.
- The official Ubuntu documentation — for anything about the operating system your server runs.
None of these will make sense cover to cover, and that's fine. You don't need to read any of them front to back. Search for the exact thing you're stuck on, read that one page, try it on your server, and get back to building. That loop — get stuck, look it up, try it, keep going — is basically the entire job, no matter how experienced you get.
You started this course with zero server experience. You're finishing it as someone who can build something, put it online under their own name, and keep it running without anyone else's help. That's not a small thing — be proud of it.
Keep the glossary handy
Bookmark the glossary. Every term from this whole course lives there in plain English, and it's the fastest way to look something up mid-project.
- Server — you rented and understood your own VPS.
- Secure — you locked it down with SSH keys and a firewall.
- Tools — you installed Node, git, and everything else you needed.
- Claude — you connected Claude Code to build with an AI partner.
- Build — you built a real project from scratch.
- Live — you gave it a domain and HTTPS.
- Keep running — you set it to restart itself and back itself up.