Before going deep on each piece individually, here is the whole list in one place — what genuinely has to happen between "the code works on my computer" and "anyone can visit it."
| Piece | What it does | Covered in |
|---|---|---|
| A domain name | The address people type or click | Domains lessons |
| DNS pointed correctly | Tells the internet which server the domain means | Domains + Connecting lessons |
| Hosting that fits your stack | A server that can actually run your kind of project | Hosting lessons |
| Your code, deployed | The actual files/app placed on that server | Connecting + stack-specific lessons |
| HTTPS / an SSL certificate | Encrypts the connection; browsers now expect this by default | Security lesson |
| A working database, if your project needs one | PHP, WordPress, and most Node apps need this connected and configured | Stack-specific lessons |
| Environment variables / secrets set correctly | API keys, database passwords — configured on the server, not hardcoded | Running-it lessons |
Email at your domain, a CDN, staging environments, and automated deployment pipelines are all genuinely useful and all covered in this category — but none of them block a first launch. A simple static portfolio site needs only the first five rows of that table. Do not let the full list feel like a prerequisite for starting; it is closer to a map of everything you might eventually need.
Different projects need different subsets of this list. A static HTML portfolio needs almost none of the database and secrets rows. A WordPress site or a Node.js API needs nearly all of it. Part of choosing hosting, covered soon, is matching the hosting to what your specific project actually requires — not over-buying capability you'll never use.
For most students' first real deployment, the honest minimum is: a domain (or a free subdomain from your host, to start), hosting matched to your stack, your code actually placed on that server, and HTTPS turned on. Everything else in this category — CDNs, staging, automated deployment — is worth learning, and worth adding once the basics are comfortable, not before.
Domains and DNS first, since almost everything else refers back to them. Then the different kinds of hosting and how to choose between them, including what things actually cost and what free tiers really offer. Then the practical mechanics of connecting a domain to hosting and getting code onto a server — FTP, SSH, control panels, Git-based deployment. Then a dedicated walkthrough for each stack taught on this site. Then CDNs and edge, security and email, and finally the operational things that matter once a site is live: staging, secrets, backups, and what to do when something breaks.