Why this site exists (and why GitHub wasn't enough)

Everything I build ends up in a repository. That’s been true for a while and it isn’t going to change — version control is where the truth about a project lives, and pushing it publicly keeps me honest in a way a private folder never did.

The problem is that a repository is a filing cabinet, not a front door.

What a repo is bad at

If you already write software, a GitHub page is a rich document. You read the commit cadence, skim the file tree, open the README, and within about ninety seconds you know roughly what the thing is, how seriously it’s being taken, and whether it works.

If you don’t write software, you see a wall of folders with names like apps and src, a file called package.json, and a graph of green squares. Nothing on that page tells you what the project does for a person. Nothing shows you a picture. There’s nowhere for a daily post to go that isn’t a commit message, nowhere to put a chart that someone can actually look at, and no way to say “here, click this and watch it move.”

That’s not a criticism of GitHub. It’s just not what GitHub is for.

What this is for

So: four sites.

This one is the hub — who’s doing this, what’s been built, and where the other three live. Each channel gets its own address, its own writing, and its own look, because the person here for orbital life support and the person here for an honest account of autistic burnout are usually not the same person, and making them scroll past each other serves neither.

The rules I’m holding myself to:

• Static and fast. Plain HTML delivered from a CDN. No accounts, no tracking, no cookie banner, nothing to consent to.
• A place for the visual stuff. Dashboards, overlays, metrics, interactive explainers — anything self-contained can be dropped in and published as-is.
• Writing that isn’t a commit message. Short notes, long essays, build logs. Whatever the thing actually needs.
• The repo stays the source of truth. The site is the readable edition, not a replacement.

What happens next

Posts, first. Then the visual pieces — the parts that were always going to be unreadable as text and have been sitting in folders waiting for somewhere to go.

If you’d rather not check back, there’s an RSS feed. It’ll be quiet until there’s something worth saying.