How I Built dout.dev (and why I did not use a framework like a normal person)
What the stack is, exactly (TL;DR: files + Node + blood)
This page was opened from file://. Chromium blocks the local CSS and JS for this site in that mode.
Preview it over HTTP with pnpm dev or pnpm preview.
Series
A series of posts about How I made it.
Posts
What the stack is, exactly (TL;DR: files + Node + blood)
The useful distinction
The honest framing
The default answer and why I ignored it
The pipeline, in one picture (because I know you're skimming)
Three constraints that shaped the grammar (because constraints are good, actually)
Three ways to slice the same posts (because one axis is never enough)
The contract (read this part)
The mistake I kept making (repeat after me: tokens first)
The goal (four non-negotiable constraints)
The distribution minimum (three files, that's it)
The problem and the usual solutions (none of which I wanted)
The short version (TL;DR for the impatient)
Why the gate exists (because you will ship shit if you don't)
The gap GitHub Pages leaves open (it's not that bad)
The term I am reclaiming (because "vibe coding" got a bad rap)
The short version (for the impatient)
The unpopular opinion (brace yourself)
The contract stays plain (because HTML should be readable)
Accessibility is not one feature (it's ALL of them)
The constraint (no backend, no excuses)
The stack I did not want
The feature and its trap
The two tools, in one paragraph
The case against most service workers