My Cloudflare setup
A domain, a place to publish, and a manageable path between the two. This is the practical side of my Cloudflare-first exploration.
Two parts of the same setup
I am interested in what makes it easier to get a small, useful site into the world and keep it understandable afterwards. Here, that means connecting domain management with a static publishing workflow.
- Buying a domain through Cloudflare: why I found it convenient, the benefits of keeping registration and DNS together, and the nameserver constraint that comes with that choice.
- My Jekyll hosting setup on Cloudflare Workers: how the repository is configured to build, check and publish static assets through a Worker.
Where Jekyll fits
Cloudflare is the domain and hosting side of this story. Jekyll turns the content and shared templates into the files a visitor reads. The two have different jobs, and understanding that boundary makes the setup easier to change.
The Cloudflare-first agenda card explains the wider interest and connects it with my earlier cloud experience. These pages follow one specific thread: this website. They are personal working notes, not an endorsement that every project needs the same platform.