Featured story
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)
- Posts
- 28
- Topics
- 30
- Series
- 4
- Months
- 4
- Featured
- 3
- Latest
- 28
About this space
This is an open, community-driven blog, a living space where ideas meet implementation. Anyone can submit articles, propose edits, or suggest improvements via pull requests. Every piece is reviewed collaboratively before publication. Read the repository governance to understand how contributions are reviewed, how disputes are resolved, and what standards each article must meet.
- No telemetry
- No cookies
- No advertising
- 0 Runtime Dependencies
Featured Articles
CSS Properties Hierarchy (Or: How I Learned Custom Properties Can Replace Preprocessors)
Context - The chaos of unorganized CSS
A Pragmatic Service Worker: Cache Strategy, Offline, No Abuse (80 Lines, No Drama)
The case against most service workers
Honest Lazy Loading: IntersectionObserver vs Native loading=lazy (The Real Difference)
The two tools, in one paragraph
Popular Topics
Recent Articles
-
CSS Properties Hierarchy (Or: How I Learned Custom Properties Can Replace Preprocessors)
Context - The chaos of unorganized CSS
-
A Pragmatic Service Worker: Cache Strategy, Offline, No Abuse (80 Lines, No Drama)
The case against most service workers
-
Honest Lazy Loading: IntersectionObserver vs Native loading=lazy (The Real Difference)
The two tools, in one paragraph
-
Accessible Scrollspy and Outline Without contenteditable (Yes, It Can Be Done)
The feature and its trap
-
A Custom Element for Syntax Highlight: Why I Wrote `pix-highlighter`
The stack I did not want
-
Pi and DeepSeek V4 Flash: The Daily Coding Loop That Costs Almost Nothing
The headline numbers
-
Client-Side Search on a Static Dataset (No Server, No Algolia, No Bullshit)
The constraint (no backend, no excuses)
-
The End of Borrowed Abstractions
The reflex that shaped software
-
Why DisplayPreferencesPopover Exists (Accessibility Is Not a Checklist, It's User Preferences)
Accessibility is not one feature (it's ALL of them)
-
How PixHighlighter Is Built (Or: I Wrote a Syntax Highlighter Because Prism Was Too Bloaty)
The contract stays plain (because HTML should be readable)
-
WCAG 2.2 AA Without ARIA-Spam (Landmarks, Heading Order, Skip-Links - That's 80% of It)
The unpopular opinion (brace yourself)
-
Modern CSS Is Enough (Container Queries, Nesting, `:has()` - No Framework Required)
The short version (for the impatient)
-
Vibe Coding With Rigor (Or: How to Use AI Without Your Codebase Turning Into a Dumpster Fire)
The term I am reclaiming (because "vibe coding" got a bad rap)
-
CI/CD Around GitHub Pages (Or: How I Got Deploy Previews Without Paying Netlify)
The gap GitHub Pages leaves open (it's not that bad)
-
Quality Gate: Linting, Formatting, and Verify (Or: How I Stopped Shipping Broken HTML)
Why the gate exists (because you will ship shit if you don't)
-
SEO Metadata Without Rituals (Or: I Read 47 SEO Blog Posts So You Don't Have To)
The short version (TL;DR for the impatient)
-
OG Images at Build Time (Or: How I Stopped Worrying and Learned to Love Sharp)
The problem and the usual solutions (none of which I wanted)
-
Feeds and Sitemaps at Build Time (RSS Is Dead, Long Live RSS. Also JSON Feed.)
The distribution minimum (three files, that's it)
-
Build Assets Pipeline (Or: How I Turned a Simple Blog Into an Image Processing Factory)
The goal (four non-negotiable constraints)
-
Design Tokens Before Pages (Yes, I Wrote the CSS Before the First Line of HTML)
The mistake I kept making (repeat after me: tokens first)
-
Progressive Enhancement as Contract (Yes, It Works Without JS. No, I'm Not Kidding.)
The contract (read this part)
-
Archives, Tags, Months, and Series (Or: How I Learned to Stop Worrying and Love Pagination)
Three ways to slice the same posts (because one axis is never enough)
-
Template Engine and Template Structure (Or: Why I Didn't Use Handlebars Like a Normal Person)
Three constraints that shaped the grammar (because constraints are good, actually)
-
Custom SSG Pipeline: From Markdown to Static HTML (Without Losing Your Mind)
The pipeline, in one picture (because I know you're skimming)
-
Why I Skipped Astro, Eleventy and Next.js (And Built My Own SSG Like a Goddamn Caveman)
The default answer and why I ignored it
-
Rebuilding dout.dev With an AI Copilot: Less Boilerplate, Same Amount of Existential Dread
The honest framing
-
CMS and Markdown Processing (Or: How I Learned to Stop Worrying and Love the Flat File)
The useful distinction
-
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)