Cloudflare Pages

Cloudflare Pages is a platform for hosting static websites and, more recently, full applications built on Cloudflare’s Workers infrastructure. It connects directly to a GitHub (or GitLab) repository, watches for pushes, and automatically builds and deploys the site whenever new code lands on the connected branch — removing the need to manually upload files or manage a traditional web server.

The core workflow is simple: a build command runs against the repository (for this vault, npx quartz build), producing a folder of static output files. A deploy command then takes that output and publishes it to Cloudflare’s global edge network (here, npx wrangler deploy, Cloudflare’s own command-line deployment tool). Because the site is served from edge locations distributed worldwide rather than a single origin server, pages typically load quickly regardless of where a visitor is located.

For projects using Cloudflare’s newer Workers-based static asset hosting (as this vault does), a small configuration file called wrangler.toml sits in the repository root, telling the deploy tool which folder holds the built site — in this case, the public/ directory that Quartz generates.

Cloudflare Pages also handles custom domains, SSL certificates, and DNS integration automatically once a domain is connected through the dashboard, which is how this vault ended up live at its own address rather than a generic subdomain.

Role in this vault

This vault’s publishing pipeline runs through Cloudflare Pages: every time a change is committed and pushed to the underlying GitHub repository, Cloudflare detects the push, rebuilds the site using Quartz, and redeploys the updated version — usually within a minute or two. This is what makes the “write in Obsidian, then git push” workflow behind this vault actually result in a live, updated website.