Thanks @jonoalderson!  🔗 **Source:** [Thanks @jonoalderson!](https://twitter.com/photomatt/status/2112511282523861149/?rw_tt_thread=True) Thanks [@jonoalderson](https://twitter.com/jonoalderson)! We need to get better at spreading the good [@WordPress](https://twitter.com/WordPress). With Fable, I reduced it from 2,910 words to 134. What do you think? AI can regenerate every page on your site. What it doesn’t regenerate is the system that connects them. An author’s bio, a product’s availability, a service URL: each appears in profiles, listings, structured data, sitemaps, feeds, and paginated archives. Without a shared record and dependency tracking, every edit leaves stale copies behind. Static deployment makes it worse, because edits never reach HTML already built. Post-publish checks can’t save you: a page can validate and still contradict the site, and knowing the right answer requires a content model. Build that model, the publishing rules, and the dependency graph yourself, and you’ve written a CMS whose spec is a list of bugs you’ve found so far. WordPress already has twenty years of answers to those questions. Use AI on top of it, not instead of it. And if you haven't yet seen our newest product, check out [@SpacefastHQ](https://twitter.com/SpacefastHQ) with AI and WordPress. 🤠  [Jono Alderson](https://twitter.com/jonoalderson) [@jonoalderson](https://twitter.com/jonoalderson) Replacing your CMS with AI-generated pages? Enjoy discovering why content management systems exist, one production bug at a time. You’ve just inherited a thousand publishing problems your CMS used to solve without you noticing. [jonoalderson.com/conjecture/you…](https://www.jonoalderson.com/conjecture/your-website-needs-a-brain/) [Posted Oct 4, 2026 at 6:52PM](https://twitter.com/jonoalderson/status/2106819710884941946), Thanks @jonoalderson!, Matt Mullenweg, 01m5cpfxh378r1fhtkj032egwc.