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
- What happens after a user enters a domain name.
- Whether your content lives on static hosting, object storage, or your own server.
- Why HTTPS is a default requirement, not an optional feature.
- What a CDN caches and what it should not cache.
- How to keep a site fast, stable, and maintainable after launch.
Recommended Reading Order
If this is your first time building a complete site, read in this order:
- What Happens During A Web Page Visit
- Domains, DNS, and Resolution Paths
- HTTP and HTTPS
- CDN Principles and Applications
- Hotlink Protection, CORS, and Host Validation
- Choosing Between Static Sites, Dynamic Sites, SSR, and Self-hosting
- What Parts Make Up A Website
- Build A Documentation Site With Docusaurus From Zero
- Static Site Deployment: Build, Hosting, Domain, and Launch
- Server Deployment: Nginx, Processes, and Reverse Proxy
- Cloudflare Setup, Proxying, and HTTPS End To End
- Aliyun CDN Acceleration For GitHub Pages
- Web Performance Basics: From First Screen To Cache Strategy
- SEO, robots.txt, sitemap, and Basic Analytics
- Image and Static Asset Optimization
- 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
- To understand the full request path first, start with What Happens During A Web Page Visit.
- If you already decided to build a documentation site, go directly to Build A Documentation Site With Docusaurus From Zero.
- If you already have a server and only want to fill in domains and Cloudflare, read Domains, DNS, and Resolution Paths and Cloudflare Setup, Proxying, and HTTPS End To End.
- To put Aliyun CDN in front of GitHub Pages for mainland China acceleration, read Aliyun CDN Acceleration For GitHub Pages.
- For OSS image hosting hotlink protection or CORS configuration, read Hotlink Protection, CORS, and Host Validation.