Building a Cloudflare-native content stack

The core idea is to keep the public site static wherever possible, then reserve dynamic work for auth, search, uploads, and editorial tasks. That makes the site simpler to reason about and faster to serve.

D1 stores the structured content graph, R2 stores media, and Pages Functions handle the thin API layer. This gives enough flexibility for a personal platform without carrying a large operational surface area.

The result is a stack that supports long-form publishing, project pages, media archives, and lightweight admin tools while staying close to the platform primitives.