Making room for small ideas

A personal site becomes much less useful when every new page has to justify its existence as a polished article.

I wanted somewhere that could hold a small observation, a build log, an interactive explanation, or a deeper case study without pretending those are all the same kind of thing. The redesign starts there.

One home, several levels of commitment

The new Writing section treats notes, essays, labs, build logs, and case studies as variations of the same basic act: making an idea inspectable.

A note can be short. A lab can lean on an interactive model. A case study should carry more evidence. None of them need a ceremonial introduction or a hero image before they can be useful.

That matters because publishing friction changes what gets published. If the smallest acceptable unit is a complete essay, most half-formed but worthwhile ideas stay in private notes forever.

Developer-shaped, not terminal-shaped

The previous design used terminal windows, command prompts, dark surfaces, and monospace almost everywhere. It clearly said “developer,” but it also made ordinary reading feel like operating software.

This version tries to signal the same background through the quality of the implementation instead:

• readable typography and deliberate hierarchy;
• fast server-rendered pages;
• accessible navigation and themes;
• small React islands only where interaction adds something;
• honest project context rather than a list of technology logos.

The code should provide the character. The page does not need to dress up as a command line.

A useful constraint

The guiding rule is simple:

Structured enough to make ideas easy to find; informal enough that ideas are easy to publish.

This note is deliberately the first test of that rule. It did not need to become a launch essay. It only needed to explain what changed and why.