Skip to main content

Website Building Learning Path From Zero

WebNotes is no longer just a place for scattered concept notes. It is now organized as a main path for building a website from zero.

This path is not mainly about whether you can write a piece of HTML. It focuses on more practical questions:

  • What do you need to understand before building your own website?
  • How do domains, DNS, HTTPS, CDN, servers, and static hosting relate to each other?
  • Why does "the website can open" not mean "the website is reliably online"?
  • Which mistakes are easiest to make during a first launch?

Who This Path Is For

The default reader is someone who:

  • Is building a personal site, documentation site, blog, or portfolio for the first time.
  • Has scattered Web concepts, but has not connected the whole path.
  • Wants to understand the minimum needed to go from an idea to a domain that is online.

This is not a complete frontend course or a complete backend course. The focus is connecting the key knowledge and decisions needed to publish a site.

Five Things To Understand First

  1. What happens after a user enters a domain name.
  2. Whether your content lives on static hosting, object storage, or your own server.
  3. Why HTTPS is a default requirement, not an optional feature.
  4. What a CDN caches and what it should not cache.
  5. How to keep a site fast, stable, and maintainable after launch.

If this is your first time building a complete site, read in this order:

  1. What Happens During A Web Page Visit
  2. Domains, DNS, and Resolution Paths
  3. HTTP and HTTPS
  4. CDN Principles and Applications
  5. Hotlink Protection, CORS, and Host Validation
  6. Choosing Between Static Sites, Dynamic Sites, SSR, and Self-hosting
  7. What Parts Make Up A Website
  8. Build A Documentation Site With Docusaurus From Zero
  9. Static Site Deployment: Build, Hosting, Domain, and Launch
  10. Server Deployment: Nginx, Processes, and Reverse Proxy
  11. Cloudflare Setup, Proxying, and HTTPS End To End
  12. Aliyun CDN Acceleration For GitHub Pages
  13. Web Performance Basics: From First Screen To Cache Strategy
  14. SEO, robots.txt, sitemap, and Basic Analytics
  15. Image and Static Asset Optimization
  16. Website Launch Checklist

Choosing Between Two Practical Paths

Path A: Static Site First

This is suitable for:

  • Documentation sites
  • Blogs
  • Portfolios
  • Introductory pages
  • Content sites with limited updates and simple interaction

It is simple, stable, cheap, and low-maintenance, which makes it the recommended starting point for a first website.

Path B: Server First

This is suitable for:

  • Login, database, or admin systems
  • API services, scheduled tasks, and file processing
  • Custom runtime logic

This route adds server management, process management, reverse proxying, and more security exposure.

The Minimum Path From Idea To Launch

Content / pages

Choose a site architecture (static hosting / server)

Create an accessible origin

Bind a domain

Configure DNS

Configure HTTPS

Add CDN / proxy layer (optional but common)

Launch checks: cache, redirects, SEO, monitoring, backups

Scope

  • The default focus is on common decisions for personal sites, documentation sites, and lightweight content sites.
  • The server deployment route is still included so the notes are not limited to static hosting.
  • This path references some existing specialized notes, but keeps only the parts that affect website-building decisions.

Where To Start