{
  "title": "Twenty-Four Years of Blog Engines",
  "date": "2026-11-17T12:00:00Z",
  "slug": "twenty-four-years-of-blog-engines",
  "type": "entry",
  "tags": [
    "blogging",
    "metablogging",
    "history",
    "webdev",
    "projects",
    "easy-blog-oven"
  ],
  "thumbnail": "/2026/11/17/twenty-four-years-of-blog-engines/2002-movable-type.png",
  "summary": "TL;DR: A self-indulgent visual tour of nearly twenty-five years of my blog across Movable Type, Blosxom, WordPress, Jekyll, and custom static generators. And how a simple bet on plain Markdown files in git outlived every platform.",
  "draft": false,
  "comments_archived": false,
  "year": "2026",
  "month": "11",
  "day": "17",
  "postName": "2026-11-17-twenty-four-years-of-blog-engines",
  "isDir": true,
  "path": "2026/11/17/twenty-four-years-of-blog-engines",
  "body": "\n**TL;DR**: A self-indulgent visual tour of nearly twenty-five years of my blog across Movable Type, Blosxom, WordPress, Jekyll, and custom static generators. And how a simple bet on plain Markdown files in git outlived every platform.\n\n\u003c!--more--\u003e\n\n\u003cnav role=\"navigation\" class=\"table-of-contents\"\u003e\u003c/nav\u003e\n\n*This is Part 1 of a two-part retrospective. In [Part 2: Baking Easy-Blog Oven v2.0 with DecafClaw](/2026/11/17/baking-easy-blog-oven-v2-0-with-decafclaw/), I cover rebuilding the static site generator in Go.*\n\n## An Occupational Hazard\n\nWeb developers writing their own blogging tools is an old occupational hazard. But I’ve been at it for almost twenty-five years, so I have more (self-inflicted) scar tissue than most.\n\nI didn't start this blog on a static generator. I launched `0xDECAFBAD` in [February 2002 on Movable Type](/2002/02/14/ooooac/)—just three months shy of a quarter century ago, which is literally half my life.\n\n\u003cfigure\u003e\n  \u003cimg src=\"./2002-movable-type.png\" alt=\"0xDECAFBAD in May 2002 running on Movable Type\"\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in May 2002, running on Movable Type (via the Wayback Machine).\u003c/figcaption\u003e\n\u003c/figure\u003e\n\nFrom the start, I wanted more than just a blog. I had this dream of a unified \"WikiLog\"—pairing the ephemeral chronological stream with an evergreen garden of ideas. In 2002, that meant running Movable Type side-by-side with TWiki, complete with [over-engineered plugins](/2002/08/19/ooobdd/) that filtered blog posts through XML-RPC to auto-link `WikiWords` to live wiki pages. \n\nIt was ambitious, but running an open wiki server on the wild web eventually collapsed under spambots and maintenance friction. The punchline, of course, is that twenty years later, that personal wiki dream won out completely—I now do all my thinking in an Obsidian vault of Markdown files. I just decoupled it: the wiki stays local and quiet, and the blog oven bakes the public stream.\n\n## The Blosxom Cutover and the Cryptic Slugs (2003)\n\nIf you poke around my earliest archive entries today, you'll still see cryptic slugs like [`ooooac`](/2002/02/14/ooooac/), [`ooooba`](/2002/02/18/ooooba/), and [`oooado`](/2002/05/07/oooado/). Those are digital scars: when I got tired of MT moving like a battleship, I rebooted onto [Blosxom](https://www.blosxom.com/) in March 2003 and declared \"[Welcome to 0xDECAFBAD v2.0](/2003/03/01/oooooa/)\".\n\n\u003cfigure\u003e\n  \u003cimg src=\"./2003-blosxom.png\" alt=\"0xDECAFBAD in June 2003 running on Blosxom\"\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2003, running on Blosxom with base-26 slugs and Agent Frank.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\nI wrote a hack to encode Movable Type's numeric database entry IDs into fixed-width base-26 slugs paired with an Apache redirect config so I wouldn't break my permalinks. [Cool URIs don't change](https://www.w3.org/Provider/Style/URI), and all that. I can't remember why I thought this in particular was a good idea. Maybe I thought the numbers were ugly? Maybe they clashed with Blosxom somehow? \n\n\u003cfigure\u003e\n  \u003cimg src=\"./2004-accessible.png\" alt=\"0xDECAFBAD in June 2004 with accessibility redesign\"\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2004, featuring the Dive Into Accessibility inspired layout.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\n## The WordPress Detour (2005)\n\nFrom Blosxom, the posts eventually traveled into WordPress in 2005 (as I recounted in my [September 2005 Colophon](/2005/09/27/colophon/)). \n\n\u003cfigure\u003e\n  \u003cimg src=\"./2005-wordpress.png\" alt=\"0xDECAFBAD in September 2005 on WordPress\"\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in September 2005, running on WordPress with PHP Markdown and Ultimate Tag Warrior.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\nWordPress solved a lot of publishing friction for a few years, but running a full dynamic, database-backed CMS for personal writing never sat right with me. I didn't want MySQL databases to backup, PHP security patches to chase, or dynamic query overhead for static essays.\n\n## The Bet on Plain Text in Git (2011)\n\nIn [June 2011, I moved to Jekyll](/2011/06/08/moved-to-jekyll/). At the time, I wrote something that turned out to be oddly prescient:\n\n\u003e *My writing here is now all stored in individual text files, formatted with Markdown, annotated with YAML metadata, and subject to revision control under git. This combination feels like it has a lot of longevity and potential for survival even beyond this current experiment with Jekyll.*\n\n\u003cfigure\u003e\n  \u003cimg src=\"./2011-jekyll.png\" alt=\"0xDECAFBAD in June 2011 on Jekyll\"\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2011, making the jump to Jekyll, GitHub, and a pile of Markdown files.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\nFifteen years later, that bet on plain Markdown files in git is still paying off. Every CMS, framework, and database engine I used before 2011 has been discarded. The pile of Markdown text files has survived untouched.\n\n## Shifting from 0xDECAFBAD to lmorchard.com (2012)\n\nAround this time, another identity shift happened. In [June 2012, I posted a farewell to decafbad.com titled \"303 See Other\"](/2012/06/15/303-see-other/) and moved my active blogging over to `blog.lmorchard.com`:\n\n\u003e *`0xDECAFBAD` is not my name. It's a pun I thought was neat, about 12 years ago. I'm not giving up the domain, but I think maybe I should start doing more things with a domain that's closer to what I call myself online and off... it turns out that there's more than one person in the `decafbad` namespace, so I thought I might start drifting closer to the one my Mom gave me. I've grown to like it, despite some misgivings earlier in life.*\n\nI'm still not entirely sure whether setting aside the cool hacker handle domain for my actual name was the \"right\" move, but here we are fourteen years later. Eventually, I reunited the old `decafbad.com` archives with the newer `blog.lmorchard.com` posts so all twenty-four years could live together in one continuous timeline (with redirects preserving the old permalinks, naturally).\n\n\u003cfigure\u003e\n  \u003cimg src=\"./2012-blog-lmorchard-wp.png\" alt=\"blog.lmorchard.com in October 2012 on WordPress\"\u003e\n  \u003cfigcaption\u003eblog.lmorchard.com in October 2012, running WordPress with the tagline \"write like no one's reading.\"\u003c/figcaption\u003e\n\u003c/figure\u003e\n\n## The Easy-Blog Oven v1 (2020)\n\nIn [May 2020](/2020/05/24/easy-blog-oven/), after outgrowing Jekyll and Gulp, I cobbled together my own Node.js static site generator called the [Easy-Blog Oven](/2020/05/25/diy-easy-blog-oven/). It wasn't an off-the-shelf framework; it was just a few hundred lines of JavaScript gluing together `marked`, `cheerio`, and ES6 template literals. \n\n\u003cfigure\u003e\n  \u003cimg src=\"./2020-blog-lmorchard-oven-v1.png\" alt=\"blog.lmorchard.com in June 2020 with Easy-Blog Oven v1\"\u003e\n  \u003cfigcaption\u003eblog.lmorchard.com in June 2020, debuting Easy-Blog Oven v1 and the canvas maze background.\u003c/figcaption\u003e\n\u003c/figure\u003e \n\nIt worked. It carried my blog for six years, through hundreds of posts, redesigns, and format experiments. But over time, the JavaScript ecosystem tax accumulated: dozens of transitive packages in `node_modules`, deprecation warnings, and an endless barrage of Dependabot alerts. Furthermore, churning through twenty-four years of archive—over 1,400 posts dating back to February 2002—took around 7 to 8 seconds.\n\nIt was time for a rewrite. Again. Because, of course it was.\n\n---\n\n*Continue to [Part 2: Baking Easy-Blog Oven v2.0 with DecafClaw](/2026/11/17/baking-easy-blog-oven-v2-0-with-decafclaw/), where I cover being talked out of Rust, rebuilding the engine in Go, and pairing with an AI agent in an afternoon of flow.*\n",
  "html": "\u003cp\u003e\u003cstrong\u003eTL;DR\u003c/strong\u003e: A self-indulgent visual tour of nearly twenty-five years of my blog across Movable Type, Blosxom, WordPress, Jekyll, and custom static generators. And how a simple bet on plain Markdown files in git outlived every platform.\u003c/p\u003e\n\u003c!--more--\u003e\n\u003cnav role=\"navigation\" class=\"table-of-contents\"\u003e\u003c/nav\u003e\n\u003cp\u003e\u003cem\u003eThis is Part 1 of a two-part retrospective. In \u003ca href=\"/2026/11/17/baking-easy-blog-oven-v2-0-with-decafclaw/\"\u003ePart 2: Baking Easy-Blog Oven v2.0 with DecafClaw\u003c/a\u003e, I cover rebuilding the static site generator in Go.\u003c/em\u003e\u003c/p\u003e\n\u003ch2 id=\"an-occupational-hazard\"\u003eAn Occupational Hazard\u003c/h2\u003e\n\u003cp\u003eWeb developers writing their own blogging tools is an old occupational hazard. But I’ve been at it for almost twenty-five years, so I have more (self-inflicted) scar tissue than most.\u003c/p\u003e\n\u003cp\u003eI didn\u0026#39;t start this blog on a static generator. I launched \u003ccode\u003e0xDECAFBAD\u003c/code\u003e in \u003ca href=\"/2002/02/14/ooooac/\"\u003eFebruary 2002 on Movable Type\u003c/a\u003e—just three months shy of a quarter century ago, which is literally half my life.\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2002-movable-type.png\" alt=\"0xDECAFBAD in May 2002 running on Movable Type\"/\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in May 2002, running on Movable Type (via the Wayback Machine).\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003cp\u003eFrom the start, I wanted more than just a blog. I had this dream of a unified \u0026#34;WikiLog\u0026#34;—pairing the ephemeral chronological stream with an evergreen garden of ideas. In 2002, that meant running Movable Type side-by-side with TWiki, complete with \u003ca href=\"/2002/08/19/ooobdd/\"\u003eover-engineered plugins\u003c/a\u003e that filtered blog posts through XML-RPC to auto-link \u003ccode\u003eWikiWords\u003c/code\u003e to live wiki pages.\u003c/p\u003e\n\u003cp\u003eIt was ambitious, but running an open wiki server on the wild web eventually collapsed under spambots and maintenance friction. The punchline, of course, is that twenty years later, that personal wiki dream won out completely—I now do all my thinking in an Obsidian vault of Markdown files. I just decoupled it: the wiki stays local and quiet, and the blog oven bakes the public stream.\u003c/p\u003e\n\u003ch2 id=\"the-blosxom-cutover-and-the-cryptic-slugs-2003\"\u003eThe Blosxom Cutover and the Cryptic Slugs (2003)\u003c/h2\u003e\n\u003cp\u003eIf you poke around my earliest archive entries today, you\u0026#39;ll still see cryptic slugs like \u003ca href=\"/2002/02/14/ooooac/\"\u003e\u003ccode\u003eooooac\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/2002/02/18/ooooba/\"\u003e\u003ccode\u003eooooba\u003c/code\u003e\u003c/a\u003e, and \u003ca href=\"/2002/05/07/oooado/\"\u003e\u003ccode\u003eoooado\u003c/code\u003e\u003c/a\u003e. Those are digital scars: when I got tired of MT moving like a battleship, I rebooted onto \u003ca href=\"https://www.blosxom.com/\"\u003eBlosxom\u003c/a\u003e in March 2003 and declared \u0026#34;\u003ca href=\"/2003/03/01/oooooa/\"\u003eWelcome to 0xDECAFBAD v2.0\u003c/a\u003e\u0026#34;.\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2003-blosxom.png\" alt=\"0xDECAFBAD in June 2003 running on Blosxom\"/\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2003, running on Blosxom with base-26 slugs and Agent Frank.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003cp\u003eI wrote a hack to encode Movable Type\u0026#39;s numeric database entry IDs into fixed-width base-26 slugs paired with an Apache redirect config so I wouldn\u0026#39;t break my permalinks. \u003ca href=\"https://www.w3.org/Provider/Style/URI\"\u003eCool URIs don\u0026#39;t change\u003c/a\u003e, and all that. I can\u0026#39;t remember why I thought this in particular was a good idea. Maybe I thought the numbers were ugly? Maybe they clashed with Blosxom somehow?\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2004-accessible.png\" alt=\"0xDECAFBAD in June 2004 with accessibility redesign\"/\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2004, featuring the Dive Into Accessibility inspired layout.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003ch2 id=\"the-wordpress-detour-2005\"\u003eThe WordPress Detour (2005)\u003c/h2\u003e\n\u003cp\u003eFrom Blosxom, the posts eventually traveled into WordPress in 2005 (as I recounted in my \u003ca href=\"/2005/09/27/colophon/\"\u003eSeptember 2005 Colophon\u003c/a\u003e).\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2005-wordpress.png\" alt=\"0xDECAFBAD in September 2005 on WordPress\"/\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in September 2005, running on WordPress with PHP Markdown and Ultimate Tag Warrior.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003cp\u003eWordPress solved a lot of publishing friction for a few years, but running a full dynamic, database-backed CMS for personal writing never sat right with me. I didn\u0026#39;t want MySQL databases to backup, PHP security patches to chase, or dynamic query overhead for static essays.\u003c/p\u003e\n\u003ch2 id=\"the-bet-on-plain-text-in-git-2011\"\u003eThe Bet on Plain Text in Git (2011)\u003c/h2\u003e\n\u003cp\u003eIn \u003ca href=\"/2011/06/08/moved-to-jekyll/\"\u003eJune 2011, I moved to Jekyll\u003c/a\u003e. At the time, I wrote something that turned out to be oddly prescient:\u003c/p\u003e\n\u003cblockquote\u003e\n\u003cp\u003e\u003cem\u003eMy writing here is now all stored in individual text files, formatted with Markdown, annotated with YAML metadata, and subject to revision control under git. This combination feels like it has a lot of longevity and potential for survival even beyond this current experiment with Jekyll.\u003c/em\u003e\u003c/p\u003e\n\u003c/blockquote\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2011-jekyll.png\" alt=\"0xDECAFBAD in June 2011 on Jekyll\"/\u003e\n  \u003cfigcaption\u003e0xDECAFBAD in June 2011, making the jump to Jekyll, GitHub, and a pile of Markdown files.\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003cp\u003eFifteen years later, that bet on plain Markdown files in git is still paying off. Every CMS, framework, and database engine I used before 2011 has been discarded. The pile of Markdown text files has survived untouched.\u003c/p\u003e\n\u003ch2 id=\"shifting-from-0xdecafbad-to-lmorchardcom-2012\"\u003eShifting from 0xDECAFBAD to lmorchard.com (2012)\u003c/h2\u003e\n\u003cp\u003eAround this time, another identity shift happened. In \u003ca href=\"/2012/06/15/303-see-other/\"\u003eJune 2012, I posted a farewell to decafbad.com titled \u0026#34;303 See Other\u0026#34;\u003c/a\u003e and moved my active blogging over to \u003ccode\u003eblog.lmorchard.com\u003c/code\u003e:\u003c/p\u003e\n\u003cblockquote\u003e\n\u003cp\u003e\u003cem\u003e\u003ccode\u003e0xDECAFBAD\u003c/code\u003e is not my name. It\u0026#39;s a pun I thought was neat, about 12 years ago. I\u0026#39;m not giving up the domain, but I think maybe I should start doing more things with a domain that\u0026#39;s closer to what I call myself online and off... it turns out that there\u0026#39;s more than one person in the \u003ccode\u003edecafbad\u003c/code\u003e namespace, so I thought I might start drifting closer to the one my Mom gave me. I\u0026#39;ve grown to like it, despite some misgivings earlier in life.\u003c/em\u003e\u003c/p\u003e\n\u003c/blockquote\u003e\n\u003cp\u003eI\u0026#39;m still not entirely sure whether setting aside the cool hacker handle domain for my actual name was the \u0026#34;right\u0026#34; move, but here we are fourteen years later. Eventually, I reunited the old \u003ccode\u003edecafbad.com\u003c/code\u003e archives with the newer \u003ccode\u003eblog.lmorchard.com\u003c/code\u003e posts so all twenty-four years could live together in one continuous timeline (with redirects preserving the old permalinks, naturally).\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2012-blog-lmorchard-wp.png\" alt=\"blog.lmorchard.com in October 2012 on WordPress\"/\u003e\n  \u003cfigcaption\u003eblog.lmorchard.com in October 2012, running WordPress with the tagline \u0026#34;write like no one\u0026#39;s reading.\u0026#34;\u003c/figcaption\u003e\n\u003c/figure\u003e\n\u003ch2 id=\"the-easy-blog-oven-v1-2020\"\u003eThe Easy-Blog Oven v1 (2020)\u003c/h2\u003e\n\u003cp\u003eIn \u003ca href=\"/2020/05/24/easy-blog-oven/\"\u003eMay 2020\u003c/a\u003e, after outgrowing Jekyll and Gulp, I cobbled together my own Node.js static site generator called the \u003ca href=\"/2020/05/25/diy-easy-blog-oven/\"\u003eEasy-Blog Oven\u003c/a\u003e. It wasn\u0026#39;t an off-the-shelf framework; it was just a few hundred lines of JavaScript gluing together \u003ccode\u003emarked\u003c/code\u003e, \u003ccode\u003echeerio\u003c/code\u003e, and ES6 template literals.\u003c/p\u003e\n\u003cfigure\u003e\n  \u003cimg src=\"./2020-blog-lmorchard-oven-v1.png\" alt=\"blog.lmorchard.com in June 2020 with Easy-Blog Oven v1\"/\u003e\n  \u003cfigcaption\u003eblog.lmorchard.com in June 2020, debuting Easy-Blog Oven v1 and the canvas maze background.\u003c/figcaption\u003e\n\u003c/figure\u003e \n\u003cp\u003eIt worked. It carried my blog for six years, through hundreds of posts, redesigns, and format experiments. But over time, the JavaScript ecosystem tax accumulated: dozens of transitive packages in \u003ccode\u003enode_modules\u003c/code\u003e, deprecation warnings, and an endless barrage of Dependabot alerts. Furthermore, churning through twenty-four years of archive—over 1,400 posts dating back to February 2002—took around 7 to 8 seconds.\u003c/p\u003e\n\u003cp\u003eIt was time for a rewrite. Again. Because, of course it was.\u003c/p\u003e\n\u003chr/\u003e\n\u003cp\u003e\u003cem\u003eContinue to \u003ca href=\"/2026/11/17/baking-easy-blog-oven-v2-0-with-decafclaw/\"\u003ePart 2: Baking Easy-Blog Oven v2.0 with DecafClaw\u003c/a\u003e, where I cover being talked out of Rust, rebuilding the engine in Go, and pairing with an AI agent in an afternoon of flow.\u003c/em\u003e\u003c/p\u003e\n",
  "sourceFile": "content/posts/2026/2026-11-17-twenty-four-years-of-blog-engines/index.md",
  "parentPath": "content/posts/2026/2026-11-17-twenty-four-years-of-blog-engines",
  "attachments": [
    "./2002-movable-type.png",
    "./2003-blosxom.png",
    "./2004-accessible.png",
    "./2005-wordpress.png",
    "./2011-jekyll.png",
    "./2012-blog-lmorchard-wp.png",
    "./2020-blog-lmorchard-oven-v1.png"
  ],
  "prevPostPath": "2026/11/13/w46",
  "prevPostTitle": "Paperclip Switches, couch boars, and the ghost MTU (Catching up: November 2 – November 13)",
  "nextPostPath": "2026/11/17/baking-easy-blog-oven-v2-0-with-decafclaw",
  "nextPostTitle": "Baking Easy-Blog Oven v2.0 with DecafClaw"
}