Attribution

What this site is made of

Where the design came from, and what it runs on.

None of this came out of nowhere. Below are the sites I kept open while designing, and every project doing real work on the page you are reading. If something is on this list it is in the build, not on a wishlist.

How it ended up like this

I set the constraints before writing any code. One column at 688px, a single grey ramp with no accent colour, four type sizes, and every page as typed TypeScript rather than markup. Constraints picked up front are ones you don't relitigate at 2am.

Some of them didn't survive. The first version had square corners, a serif display face and uppercase mono labels, and in a column this narrow they shouted. The display type went, and hierarchy moved to weight and colour. DESIGN.md keeps a list of what was removed and why, so I don't rebuild it by accident.

It runs on Next.js 16 and React 19, styled with Tailwind v4. I plan, build and review with Claude Code, which is all AI-native means here. It buys pace. The review is what stops the pace turning into a shortcut.

What I wanted was a site that loads fast, works with a keyboard and a screen reader, and shows the work instead of describing it.

Where the ideas came from

The stack

Type and icons

What it runs on

The longer version

I wrote up how the whole thing was put together, including what I tried first, in the build logThe build log for this site, stack and decisions included.. If you came for the hardware and the apps rather than the credits, those are on the uses pageThe hardware, editor, and tools I actually use..