2026-07-01

Bloom operating model

How Bloom separates source control, website runtime, content operations, and Cloudflare services.

Bloom starts with a simple split: the private repository is the source of truth, and Cloudflare is the public runtime.

The repository owns code, content, design, documentation, and deployment history. Cloudflare owns DNS, TLS, edge delivery, security controls, cache behavior, and future runtime services.

This keeps the first version light while leaving room for growth.

Initial operating loop

1. Write or edit content in Markdown.
2. Run the site locally with npm run dev.
3. Build with npm run build.
4. Deploy with Wrangler or a private repo CI workflow.
5. Monitor Cloudflare deployment, analytics, and security events.

Why this stays flexible

Static pages handle the public website. A Worker can later add API routes, form handling, redirects, personalization, or authentication gates. Cloudflare D1, KV, R2, Turnstile, Web Analytics, and WAF can attach without moving the site to another host.

SEO, GEO, and AEO base

Every durable page should have a direct answer, a canonical URL, a clear title, a plain description, structured metadata, and a stable publishing date. This makes the page useful to people, search crawlers, and answer engines.