Bootstrapping melltron.build

This site has two jobs: a build log (this) and a lab — a registry of tools and experiments that each run on their own *.melltron.build subdomain.

Decisions

Static assets behind a thin Worker. Content is Markdown, rendered to HTML by a small Python script and committed. The Worker only enforces the canonical host, security headers, and cache policy. No framework, no build step at the edge — the deployed artifact is exactly what’s in the repo.

One Worker per lab app. Experiments break. Isolating each on its own Worker and subdomain means a bad deploy in the lab can’t take the root site down, and each app can be retired without touching anything else. The root only keeps a registry pointing at them.

Personal accounts, not company ones. Repo, DNS, and Cloudflare account are personal. Mixing a personal domain into company infrastructure blurs ownership — it surfaces in IP assignment, in due diligence, and on the day anyone leaves. Separating it costs nothing now.

Status

Part	State
Root site	live
Feed / sitemap	live
Lab apps	none yet