Blog

Rebuilding This Site with an AI Pair

Why I'm moving off WordPress to a static, Markdown-in-git Astro site — and letting an AI do the commits.

After thirteen years on self-hosted WordPress, I’m rebuilding this site from scratch. The new stack is boring on purpose: Astro, static output, Markdown content collections in a git repo, deployed to Cloudflare Pages on push.

Why bother

My priorities, in order, are maintenance, backup, and security. WordPress is a database, a PHP runtime, and a plugin surface I have to keep patched. A static site is a folder of HTML. There’s almost nothing to attack and nothing to back up beyond a git repo I already have.

The part I’m actually excited about

Content is plain Markdown, so I can have an AI edit the site by committing to the repo:

// Every post is just a typed file on disk.
const post = {
  title: "Rebuilding This Site with an AI Pair",
  pubDate: new Date("2026-07-06"),
  tags: ["astro", "ai", "meta"],
  comments: true,
};

Every change is a commit. Every commit is reviewable. Nothing happens to the site that isn’t a diff I can read.

The dream isn’t “AI runs my website.” It’s “AI drafts, I review, git remembers.”

More soon — including how the WordPress export actually went.