WordPress Just Turned Into Succession Meets Below Deck

How does software that once powered the White House become something people ask, “Is that still around?”And what happens when the answer is more interesting than they expected?Drupal started with a student and a website for his friends. It grew into a global community... and powered some of the most influential websites in the world.Now, twenty-five years later, Acquia is putting Drupal at the center of its AI future.So is this Drupal’s renaissance?To answer that, we need to talk about what it built... and what Acquia wishes it had never sunsetted.

The WordPress Drama Saga Continues.... Matt Mullenweg was out for roughly 33 hours. During that window, two Automattic executives reportedly signed each other’s severance agreements... with $8.15 million in potential compensation at stake. AKA A Golden ParachuteThis isn’t a birthday card. “You sign mine, I sign yours” sounds very different when millions of dollars are involved.In this episode of Headless, Hayden breaks down the September 2026 WordPress drama at Automattic, the company behind WordPress.com: the golden-parachute agreements involving Mark Davies and Andy Missan, the board crisis, and what the reporting actually establishes.In this episode:• The reported 33-hour timeline and reciprocal severance agreements• Why signatures and authorization are different questions• The board-page changes and Automattic’s reported explanation• The Repository’s report of unanswered employee questions and a closed anonymous forum• The Reddit comments that sharpen the story—and where speculation outruns the evidence• The questions WordPress users, agencies, and clients should askThe $8.15 million is reported potential compensation, not a confirmed payout. The employee account comes from one anonymous source and has not been independently verified by Headless. This episode does not claim a resolved legal outcome.Has this changed anything in your actual work—or just added another conversation with a worried client? Tell me in the comments.Subscribe to Headless for WordPress news, CMS and DXP analysis, and the people making website software considerably more dramatic than it needs to be.0:00 The Executive Compensation Dilemma1:38 The 33-Hour Window of Uncertainty3:08 Navigating the Online Comment Wars6:15 The Internal Reality at Automattic8:57 The Confusion of the Board Page#WordPress #MattMullenweg #Automattic

Matt Mullenweg was placed on involuntary paid leave by Automattic’s board on September 9. By September 11, he was back as CEO with the board’s support.What caused the removal—and the rapid reversal—still hasn’t been publicly explained by the reporting reviewed for this episode.Then, amid questions about Automattic’s leadership and the future of WordPress, Matt published a “Major Life Announcement.” It was about his offer on a houseboat.Behind the absurd timing is a serious governance question: when Automattic’s board temporarily removed its founder, how much power did it actually remove?WordPress is not a single organization. The open-source software, Automattic, WordPress.com, the WordPress Foundation, the trademark, and WordPress.org are connected—but they are not interchangeable. Automattic’s own account identifies Matt as the owner of WordPress.org, making the separation between corporate authority and personally controlled infrastructure worth examining.That matters because access to WordPress.org has already been used as leverage in the dispute with WP Engine. A court later ordered that access restored, but the episode demonstrated the practical power surrounding services that much of the ecosystem depends upon.This episode breaks down:• Matt Mullenweg’s leave and return• What remains unexplained about the board’s reversal• Who controls the different pieces of WordPress• The previous restriction of WP Engine’s WordPress.org access• Why the houseboat announcement landed so badly• The real cost of leaving the WordPress ecosystem• Why governance stability may become a premium CMS featureThe allegations of a coup and Silver Lake’s involvement remain unproven. An inactive Slack account does not establish anyone’s employment status, and the available reporting does not prove that personally controlled infrastructure was used during this week’s board dispute.The documented timeline is already strange enough.Tell me in the comments: has the turmoil around WordPress and Automattic changed a real client conversation, hosting decision, or platform recommendation?Subscribe to Headless for sharp, practical coverage of WordPress, CMS platforms, AI agents, digital governance, and the machinery underneath the modern web.Join the conversation:https://www.reddit.com/r/HeadlessPodcast/A week of WordPress drama: the CEO's exit and return raises serious questions about power and ownership.The recent WordPress drama involving Matt Mullenweg’s temporary departure and swift return has left many users questioning the underlying stability of the platform. Beyond the headlines, the corporate governance of the project is under scrutiny, particularly regarding how power is distributed when leadership is in flux.The sudden announcement of a houseboat project, amidst the chaos, serves as a strange backdrop to these deeper structural concerns. It forces a conversation about company ownership and transparency that the ecosystem cannot ignore. Understanding these shifts is essential for anyone relying on the software for their livelihood.Subscribe for weekly platform breakdowns, and share your thoughts on the future of open source governance.#WordPress #MattMullenweg #Automattic

Webflow launched Source. Acquia already has Source. Somewhere, an SEO manager has quietly closed their laptop.In Episode 3 of Headless, Hayden connects four developments from the week of August 31–September 4, 2026:• Webflow’s Source announcement—and its awkward naming overlap with Acquia’s existing platform• Optimizely’s Virtual Teammates and the move from Opal to Mark• Salesforce completing its acquisition of Contentful• The Justice Department backing OpenAI’s fair-use argument in the copyright dispute involving The New York TimesThe bigger question: as AI agents start doing more of the work, who controls their permissions, their workflows, and the content they depend on?Expect practical questions for your next vendor call, web-development nostalgia, and Enterprise Voltron—where each leg has a separate renewal date.The Comment Section returns with shout-outs to u/Global-Signature757 and u/zubrinovic. Plus quick honorable mentions covering Anthropic commerce agents, Contentstack’s publishing fix, and Astro support in Optimizely CMS 13.Join the conversation:https://www.reddit.com/r/HeadlessPodcast/Bring your hot takes, firsthand experiences, and stories worth investigating. Your comment could appear in a future episode.Selected sources:Webflow: https://webflow.com/blog/introducing-source-by-webflowAcquia: https://docs.acquia.com/acquia-source/acquia-source-product-guideOptimizely: https://www.optimizely.com/company/press/virtual-teammatesOpticon: https://www.optimizely.com/field-notes/articles/ai-platform-built-for-whats-nextSalesforce: https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-contentful/Copyright reporting: https://apnews.com/article/dbb22e8e02c660ee5a8644915dec39a4Context: Webflow Source was announced as a limited research preview. The DOJ filing is an argument submitted to the court, not a ruling.

The CMS is having an identity crisis.Salesforce is buying Contentful. Cloudflare built an AI-native “spiritual successor to WordPress.” Drupal believes its famously intense governance model may be exactly what AI agents need. Meanwhile, WordPress sites are being recruited into global cybercrime operations while Automattic and WP Engine continue turning open-source governance into prestige television.Hayden also returns to the comments section, where one AI agent broke 18 Webflow blog posts, a photographer built his own CMS out of spite, and a Reddit user explained why self-discoverable APIs may finally get their moment.This week on Headless:• Why content is becoming infrastructure for AI• Whether agents need a new kind of CMS• How Drupal became Batman with a spreadsheet• Why abandoned WordPress sites still matter• Whether the CMS is dying or simply disappearing into the wallsFollow Headless for weekly CMS, DXP, AI, and web infrastructure news without the vendor-approved personality transplant.Have a take, correction, confession, or deeply unhinged CMS story? Send it Hayden’s way. The comments section is officially part of the show.

Your CMS has a new user.And it’s not human.This week on Headless, we’re connecting a handful of stories that look unrelated until you zoom out.WordPress 7.1 just shipped. Storyblok plugged directly into Claude. Optimizely fixed an AI agent that could accidentally wipe a page while confidently telling you everything went great. Salesforce is expanding something literally called “Headless 360.” And Contentful is asking a wonderfully ominous question: What if your next visitor isn’t a person?Individually, they’re product updates.Together, they point toward something much bigger.The CMS is evolving from software humans use to infrastructure AI uses.We break down what that means for WordPress, headless CMS, DXP, MCP, AI agents, structured content, governance, and the increasingly important question of whether the future of “headless” has anything to do with websites at all.Plus: why Agent Experience might become the next battleground for CMS vendors, why boring things like metadata and permissions are suddenly very sexy, and one prediction about what every enterprise CMS RFP is going to include within the next 18 months.Stories from this episode:WordPress 7.1 “Mary Lou”Released August 19 with responsive styling, collaboration improvements, media upgrades, new APIs, and more.https://wordpress.org/news/2026/08/mary-lou/Storyblok joins Claude’s Connector DirectoryStoryblok can now connect directly to Claude through a remote MCP server with OAuth-scoped access.https://www.storyblok.com/mp/storyblok-on-claude-connector-directoryOptimizely CMS 13 + Opal updatesIncluding the extremely important fix where an AI-powered CMS tool could empty a Visual Builder page and still report success. Computers remain undefeated.https://support.optimizely.com/hc/en-us/articles/44937048830221-2026-Optimizely-CMS-13-release-notesSalesforce expands Headless 360Salesforce is turning capabilities across its platform into services that authorized AI agents can discover and use through open standards like MCP.https://www.salesforce.com/news/stories/expanding-headless-360-enterprise-capabilities/Contentful: “What if your next visitor isn’t a person?”Contentful and Apply Digital dig into AI agents, discovery, and what it means to make content understandable to machines.https://www.contentful.com/events/agentic-shift-website/Headless is a weekly look at what’s happening across CMS, DXP, composable architecture, content infrastructure, and the increasingly weird future of the web.Not just what happened.Why it matters.