q1rk  //  log

building the record

The first thing q1rk had to prove was itself. A record of building that you can't add to without a developer isn't a record — it's a brochure. So the rule came before the design: adding a page, a log, a menu item can never mean touching markup in five files.

It runs on Next.js, App Router. Navigation is defined once, in a single config. Every post is a markdown file dropped into one folder — the route, the metadata, the search index all derive from it. Write a file, it's live. No second step.

That constraint did more than save time. It killed the excuse. When publishing costs nothing but the writing, the only reason not to ship is that the work isn't done — which is the right reason, and the only one.

The look is ported straight from the landing page that started this: warm near-black, one phosphor accent used like punctuation, a serif for the human voice against a mono for the machine. The tension between those two fonts is the whole argument, so nothing else competes with it.

It builds clean and deploys on a push. That's the bar for everything here. If it doesn't run, it doesn't count.

all logs