← All writing

Why This Site Has No Framework

March 20, 2026 · 1 min read

This site is generated by about 500 lines of plain Node.js. No React, no Next.js, no Jamstack starter kit, no npm install that takes longer than the flight of stairs to make coffee. Here's the whole pipeline:

  1. Content lives in content/ as markdown files (posts) and JSON (site info, bookshelf).
  2. node scripts/build.js reads it all, runs it through a small hand-rolled markdown parser, and writes plain HTML into public/.
  3. node scripts/server.js serves public/ locally with zero dependencies.

That's it. No build tool to configure, no dependency updates to babysit, nothing to break in six months when a package I've never heard of gets deprecated. If I want a new post, I add a markdown file. If I want to redesign, I edit one CSS file. If Goodreads changes its RSS format again, I fix one script and nothing else notices.

I don't think everyone should build their own static site generator — reach for something like Eleventy or Hugo if you want, they're good at this. But for a site this small, writing the 500 lines myself means I understand every part of it, and "it broke" is never followed by "and I have no idea why."