Static sites don't need complex deployment pipelines. No Docker containers. No CI/CD YAML files. No server management. Just git push and you're live.
The Problem
Most hosting is overkill. WordPress for a landing page that changes twice a year. A VPS for a blog with 100 monthly visitors. $20/month for infrastructure that sits idle 99% of the time.
Even "simple" deployment platforms require configuration: build commands, environment variables, output directories. You spend more time debugging deployment than building the site.
The Solution
Cloudflare Pages. Free tier includes SSL, global CDN, and unlimited bandwidth. Deploy with one command. No build configuration needed for pure HTML/CSS/JS sites.
How It Works
Three commands from your site directory:
# Install Wrangler CLI (Cloudflare's deployment tool) npm install -g wrangler # Deploy current directory to Cloudflare Pages npx wrangler pages deploy . --project-name=mysite --branch=main # Verify deployment curl https://mysite.pages.dev
The deploy command pushes all files to Cloudflare's edge network. No Git integration required—direct upload from your local directory. Site goes live at project-name.pages.dev immediately.
For custom domains, add a CNAME record pointing to project-name.pages.dev. SSL provisions automatically via Let's Encrypt.
Results
Key Lessons
- Static sites scale infinitely. No database queries, no server-side processing. Cloudflare's CDN handles millions of requests without breaking a sweat.
- Cloudflare CDN beats AWS/Azure for speed. 200+ edge locations vs. AWS CloudFront's 400+, but Cloudflare's network is purpose-built for low latency. Most users see sub-50ms response times.
- No build step means no build failures. Pure HTML/CSS/JS sites deploy every time. No npm dependency hell, no webpack version conflicts, no mysterious build errors at 3am.
