Drupal 9 marketing site, ~180 pages, 40 blog posts, the one contractor who knew it left. PHP and module updates were piling up, so instead of going to Drupal 10 I pointed Claude Code at it and rebuilt in Next.js.

What it did:

• Read the modules and theme to map content types, fields and views, then pulled the actual content out via JSON:API into MDX files. Fields became frontmatter, embeds became components.
• Rebuilt the theme as React components, close enough that nobody noticed
• Recreated the blog/tag listings as filtering over the files
• Wrote the redirect map for old URLs
• Set up SST with OpenNext: CloudFront, S3, Lambda, Route53 in one config. sst deploy, done.

Where it struggled: ~600 images in weird paths took a few passes, webforms had to be rewritten against Lambda + SES (and I lost spam protection for a week without noticing), and it kept trying to add a headless CMS until I told it Markdown in git IS the CMS.

Drupal's been off two months. Hosting went from $90/mo to ~$4. Content changes are now "open Claude Code, describe the edit, review PR, merge."

Downside: nobody non-technical can edit anything without me. Fine for us now, but I'm wondering if I've just made myself the new single point of failure, same as the contractor was.

What am I missing? Anyone running content-in-git + AI as the CMS past a couple hundred pages?