I migrated a website with 800+ articles from @WordPress to a fully static HTML site managed with Claude Code. A few months later, I went back to WordPress. At first, it felt like the obvious move. Why keep a CMS if AI can manage the entire site? On paper, the advantages were clear: - Extreme performance (no database, no plugins) - Full flexibility (edit HTML/CSS/JS directly) - Better security (almost no attack surface) - Claude could even suggest internal links using Search Console data I genuinely thought I had found something better. Then I started managing the site every day. And the reality hit. Want to change 2 lines in an article? WordPress: open, edit and update. Done in 20 seconds. Static + Claude: find the file, understand the context, make the change, check that nothing broke. Several minutes. Same problem when deleting multiple articles or updating categories, pagination, sitemap, internal links, redirects… The usual answer is: “Just build scripts and agents.” True. But the moment you start building all those automations, you’re basically rebuilding your own CMS. So the real question is no longer: “Can AI replace WordPress?” It’s: “Can it handle all the small daily operations quickly and reliably?” On a small site : yes, static + AI is excellent. On an editorial site with hundreds of articles that you update regularly : it’s a different story. You end up managing HTML + categories + pagination + sitemap + search + redirects + internal linking + deployment + prompts… Your website becomes a software project. After several months living without WordPress, my conclusion is simple: WordPress isn’t dead. Because the real strength of a CMS is that it automatically handles hundreds of small things you no longer have to think about. Anyone else tried going fully static with AI on a large content site?