A Note on Cloudflare Pages

Deployed three sites to Cloudflare Pages this week on the free tier. Build times are fast, the GitHub integration is seamless, and the global CDN means the sites are genuinely fast from anywhere. The free tier is generous enough that it covers everything a personal publishing operation needs without qualification.

The one friction point is the build configuration UI, which has improved but still requires knowing what you are doing. If you point it at the wrong output directory the deploy succeeds and the site is empty. There is no obvious error. You have to know to check the output directory setting.

The other thing worth noting: Cloudflare's DNS is excellent and integrating a custom domain through their dashboard is faster than any other registrar or host I have used. Point the nameservers, add the domain in Pages, done in under five minutes.

Running this site on Fastpack — a custom Go static site generator built this week. Zero dependencies, six millisecond builds, Go standard library only. The Cloudflare build environment has Go pre-installed so the build command is go run main.go and the output directory is dist. That is the entire configuration.

No lock files, no npm, no framework preset. Framework: None. It is a relief.