What belongs here
  • Projects that started from a real need, not just a tutorial outcome.
  • Cloudflare-native builds and edge experiments that may grow into fuller products.
  • Small notes on structure, rollout, and useful tradeoffs when a project earns them.
What stays out of v1
  • Private home tooling mixed into the public site.
  • An exhaustive dump of every unfinished idea.
  • A heavy framework stack before the site actually needs one.
Principles

A few defaults that keep the domain healthy.

Keep the apex calm

The main site should explain the work quickly, not absorb every future app, dashboard, or experiment.

Promote with intent

A project earns its own subdomain when it has a stable purpose, a distinct audience, and a surface worth revisiting.

Separate privacy cleanly

Private tools can grow later behind Cloudflare Access instead of leaking complexity into the public hub.