Are We in Drupal's Renaissance?  🔗 **Source:** [Are We in Drupal's Renaissance?](https://youtube.com/watch?v=7ISddVI0SgE&is=xKBKfaCxv3CPMgyY) > [!note]+ Document Notes > tags: [drupal, acquia, agentic-ai, content-governance, open-source-business-models, devrel] > author: Hayden (Headless) > source: Headless (YouTube) > reference: https://www.youtube.com/watch?v=7ISddVI0SgE > date created: 2026-09-28 08:17 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > > [!warning] Auto-caption artifacts and script ambiguities. The Drupal mascot's name (Druplicon) > > is captioned as "the Drupal con." The video names "Mautic" as the target of two different > > acquisitions serving two different purposes (marketing automation in 2019; "digital assets and > > product information" two years later) — this reads like a script or captioning error repeating > > one company name for what was likely a second, different deal; the source material does not > > resolve which. "Thomas Skola" and "Agile One" (the 2019 customer-data-platform deal) are > > unverified spellings. Verify company names, acquisition targets, and dates against Acquia's own > > record before citing any of this. > > # 🏷️ Title: Are we in Drupal's Renaissance? > <!-- deep-read:sections start --> ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 Quick reference - Source: https://www.youtube.com/watch?v=7ISddVI0SgE (Headless, published 2026-09-27, last caption at 13:50) - Dries Buytaert — Drupal's founder and Acquia's co-founder and CTO; his own blog posts and public announcements are the primary source for nearly every date and claim in this video - Acquia — the commercial company built around Drupal, co-founded with Jay Batson in June 2007 - Drupal Association — the nonprofit steward of drupal.org and Drupal's community infrastructure, named as the recipient of Acquia's Fair Trade contribution ## 📝 Summary - **What this is.** A 14-minute narrated video essay (Headless, published 2026-09-27, last caption at 00:13:50) tracing Drupal's 25-year history through the lens of one question: why Acquia's September 14, 2026 rebrand puts Drupal, not its own product names, back under the company logo. - **The claim.** The narrator argues the rebrand is not new positioning bolted onto old software. It is Acquia catching its brand up to product work already shipped: Drupal CMS 1.0 (Jan 2025), Drupal Canvas 1.0 (Dec 2025), Acquia Source (Nov 2025), Source Workspace and Acquia AI (April 2026), all released before the rebrand made any of them visible under the Drupal name. - **Why it matters.** The video names a real, specific failure mode: a platform can modernize for years while the people who last touched it years ago still ask "is that still around?" That gap between shipped capability and public perception is a DevRel-shaped problem, not just a marketing one. - **Key stakeholders.** Dries Buytaert (founder, quoted only through his blog posts and public announcements, never on camera), Acquia (the commercial vendor), the Drupal Association (nonprofit steward, funding recipient), enterprise customers weighing managed versus self-managed tiers, and the volunteer contributors whose work (Views, Drupal CMS, Canvas) is credited as happening in parallel with Acquia's commercial moves. - **Risks and tradeoffs.** The narrative leans entirely on Acquia's and Dries' own framing of its history, including its own regretted decision (killing Drupal Gardens). No competitor, analyst, or independent customer voice appears. The evidence for Drupal's continued enterprise relevance is entirely from 2009 (The Economist, the Grammy Awards, whitehouse.gov); no 2020s-era brand example is offered to counter the "still around?" skepticism the video itself raises. - **Bottom line.** A vendor's rebrand read charitably as a genuine correction of a perception lag, built on real shipped features and a real funding commitment to the open-source foundation, but told entirely from that vendor's own historical record with no outside check. ## 📖 Main content - **The origin story is deliberately small-scale.** Dries Buytaert built a website in 2000 for himself and friends sharing an internet connection in Antwerp, released the underlying software in January 2001, and it became Drupal. A typo turned "Dorp" (Dutch for village) into drop.org. - **The community formed around a saying that the video treats as load-bearing.** "Come for the code, stay for the community" appears twice, once early and again in the closing line, framing the whole 25-year arc as a community story with a commercial company grafted onto it later, not the reverse. - **MTV is the origin of Acquia's business case (00:02:18).** Dries, still finishing his PhD, helped MTV with a Drupal support problem for free. That gap between "you can download this software" and "you need help running it for something that matters" is what became Acquia, incorporated with Jay Batson in June 2007. - **The founding separation of concerns is stated explicitly and is the video's strongest artifact.** Dries' original 2007 announcement said Acquia would not close-source Drupal; the business would live in services around the open-source project, not inside it. - **Acquia's first expansion (Jan 2009) already shows the managed-versus-custom tension that defines the whole video.** Acquia moved from supporting only its own curated Drupal package to supporting all of Drupal 6, including customers' own custom code, because customers' real websites were messier than any curated package. - **Drupal Gardens is the video's one unambiguous regret, sourced to Dries himself.** A no-code, browser-only way to build a Drupal site, it reached over 100,000 sites before Acquia shut it down to focus resources on enterprise features (Cloud Site Factory). Dries later published a post titled, in his own words, about the product Acquia should not have killed. - **The 2019-2021 acquisition run is where the video's own account gets confused (00:05:53).** It names Mautic for marketing automation in 2019, a majority investment from Vista, a deal for a customer data platform ("Agile One"), and then, two years later, another acquisition of "Mautic" for digital assets and product information. Two different deals attributed to one company name is very likely a script error, not two real Mautic acquisitions. - **Community-built features earning a path into core is the throughline the video uses to argue Drupal never stopped moving.** Views started as a contributed module and merged into what became Drupal 8 in 2012. Drupal CMS 1.0 (Jan 2025) packaged core with search, media, and SEO so builders don't have to assemble it themselves. Drupal Canvas 1.0 (Dec 2025) added a visual, in-browser page builder. - **The reputation-lag anecdote is the pivot of the whole essay (00:07:22).** At a Drupal AI event in New York, someone reportedly asked "Drupal? Is that still around?" The narrator's argument: the software modernized faster than its reputation, and this rebrand is Acquia trying to close that specific gap rather than open a new one. - **Acquia Source reintroduces the market Gardens once served, this time deliberately split into two tiers.** Source CMS is the fully managed path (Acquia runs the Drupal back end; the team builds within it, cannot modify core, cannot install drupal.org contributed modules, can extend via custom components and APIs). Cloud Platform is the self-managed path for teams that need full control, including custom modules. The video's own example is a university that plausibly needs both: a heavily customized main site and a simple alumni campaign site. - **Acquia AI and Source Workspace (April 2026) extend the platform into agent management.** The video states, in one sentence, that users can create and manage agents in the browser with permissions and human review for higher-risk actions. No further detail on how "higher-risk" is defined or enforced is given. - **The June 2026 argument is the video's central thesis about AI and content.** Dries' own website (over 1,500 posts, 10,000 photos) is the example: an AI agent can help make changes, but Drupal still holds the content and the access controls around who can edit, what's approved, and what changed between versions. The claim is that AI makes producing content easier while increasing the importance of managing what gets produced. - **The Fair Trade funding commitment is concrete and checkable in a way most of the video isn't.** The Drupal Association describes 2% of eligible Acquia partner deals going to the Association, funded from Acquia's margin rather than a customer surcharge or a cut of partner revenue. - **The closing argument is a callback, and it's the video's tightest piece of reasoning.** Dries' original 2007 startup announcement already described Drupal as a place to keep managed content that other tools and websites could access via APIs and access controls. Nineteen years later, per the narrator, the other tool accessing that content might be an AI agent. The mechanism (structured content plus access control, exposed to something outside the CMS) is presented as unchanged; only what's on the other end of the API has changed. - **What's unverified.** Every substantive quote and date traces to Dries Buytaert's own posts and announcements, relayed by the narrator, not shown on screen or independently sourced. No customer, competitor, or analyst appears. The only brand-name proof of Drupal's continued relevance (Economist, Grammys, whitehouse.gov) is from 2009, seventeen years before the "is that still around?" question the video itself raises. ## 🗒️ Notes #### ⏱️ [00:00:02](https://www.youtube.com/watch?v=7ISddVI0SgE&t=2) The setup - Frames the whole video as a question: how does a company that spent years making Drupal less visible in its brand suddenly bet its AI future on it. - Points at Acquia's rebrand putting "Powered by Drupal" under the logo as the thing needing explaining. - Names a killed product (Drupal Gardens) as the thread the story runs through. #### ⏱️ [00:00:51](https://www.youtube.com/watch?v=7ISddVI0SgE&t=51) Origins: Y2K to drop.org - Sets the scene with Napster, AOL Instant Messenger, and MP3 folders to place the year as 2000. - Dries Buytaert, a student in Antwerp, built a small shared site for his friend group; released the software behind it in January 2001. - A typo meant to register "Dorp" (village) produced drop.org; the project became Drupal. - The mascot, referred to in the transcript as "the Drupal con" (almost certainly Druplicon, the actual name), became a community fixture with local variants. > [!quote] > By 2005, people were meeting in Antwerp for the first ever Drupal con. #### ⏱️ [00:02:18](https://www.youtube.com/watch?v=7ISddVI0SgE&t=138) The saying, MTV, and the founding of Acquia > [!quote] > Come for the code, stay for the community. - MTV's support problem, handled free by Dries while finishing his PhD, is framed as the birth of the biggest business opportunity in the story. - June 2007: Dries and entrepreneur Jay Batson incorporate Acquia. > [!quote] > Drupal remained the open source project, and Acquia was the business built around helping organizations use it. - Dries' original announcement explicitly said Acquia would not close-source Drupal. - January 2009: Acquia expands support from its own curated package to all of Drupal 6, including customers' own custom code. - Before Drupal turned 10, it was running The Economist, the Grammy Awards, and (in 2009) whitehouse.gov. #### ⏱️ [00:04:28](https://www.youtube.com/watch?v=7ISddVI0SgE&t=268) Drupal Gardens, the regret, and the DXP acquisitions - Drupal Gardens: build a Drupal site with no code and no infrastructure to manage. Reached 100,000+ sites before Acquia shut it down. > [!quote] > Years later, Dries published a post called the product we should not have killed. - His stated reason: enterprise customers needed custom integrations, governance, and fleet-management tools (Cloud Site Factory); a young company couldn't fully fund both paths, so it chose enterprise. - 2019: Mautic acquisition (marketing automation), a majority investment from Vista, and a deal for customer data platform "Agile One." - "Two years later," per the transcript, another acquisition of "Mautic" for digital assets and product information: almost certainly a different, unresolved company name repeated in error. #### ⏱️ [00:06:38](https://www.youtube.com/watch?v=7ISddVI0SgE&t=398) Community ships while Acquia expands - Views began as a contributed module; merged into what became Drupal 8 in 2012. - January 2025: Drupal CMS 1.0 packages core with search, media handling, and SEO so builders don't assemble those separately. - December 2025: Drupal Canvas 1.0, a visual, in-browser page builder. - Framed as two parallel tracks: Acquia's commercial portfolio growing, and the open community project getting easier to use, neither one guaranteeing the other gets noticed. #### ⏱️ [00:07:22](https://www.youtube.com/watch?v=7ISddVI0SgE&t=442) The reputation gap > [!quote] > Drupal? Is that still around? - Attributed to someone overheard by Thomas Skola (spelling unverified) at a Drupal AI event in New York. - Dries shared his own response to this in a post in May 2026: the software modernized faster than its reputation. - The narrator ties this directly to why the rebrand needed to happen: shipped capability isn't visible until the brand says so. #### ⏱️ [00:08:06](https://www.youtube.com/watch?v=7ISddVI0SgE&t=486) Acquia Source and the two-path model - November 2025: Dries introduces Acquia Source, explicitly revisiting the need Gardens once addressed. - Source CMS: the managed path. Acquia runs the Drupal back end; the customer's team builds and manages the site inside that service. - Cloud Platform: the path for teams needing full control, including custom modules. - The video's own example: a university with a heavily customized main site and a separate, simple alumni campaign site, same CMS, two different jobs. #### ⏱️ [00:09:31](https://www.youtube.com/watch?v=7ISddVI0SgE&t=571) Source Workspace, Acquia AI, and the governance argument - April 2026: Source Workspace connects content management, digital assets, web governance, and AI agents in one working environment. > [!quote] > The company said users could create and manage agents in the browser with permissions and human review for higher risk actions. - June 2026: Dries' own site (1,500+ posts, 10,000+ photos) as the worked example. An AI agent can make changes; Drupal still holds the content and the access controls (who can edit, what's approved, what changed between revisions). > [!quote] > AI makes producing things easier while increasing the importance of managing what gets produced. #### ⏱️ [00:10:57](https://www.youtube.com/watch?v=7ISddVI0SgE&t=657) The rebrand and the funding commitment - September 14, 2026: Acquia's homepage moves from "digital experience platform" to "agentic content platform," with Drupal returned to visible prominence in the brand. - Dries' stated reason for the rebrand: the products evolved faster than people's awareness of them. - The Drupal Association's Fair Trade initiative, described back in June: > [!quote] > 2% of eligible partner deals goes to the association. - Funded from Acquia's margin, not a customer surcharge and not a cut of partner revenue. #### ⏱️ [00:11:41](https://www.youtube.com/watch?v=7ISddVI0SgE&t=701) Source CMS's boundaries, and who they're fine for > [!quote] > In Source CMS, you cannot modify the underlying Drupal code or install contributed modules from drupal.org. - Extension is possible through custom components and APIs, but the tier has hard boundaries. - The narrator's argument: if a university's central web team already approves every module, individual site owners weren't choosing their own software anyway, so the boundary costs them nothing they were actually using. #### ⏱️ [00:13:07](https://www.youtube.com/watch?v=7ISddVI0SgE&t=787) The portability promise and the closing callback > [!quote] > Export a complete Drupal site, including its code, configuration, and content, and run it elsewhere. - Stated as Dries' public promise from December 2025, offered as the answer to lock-in concerns about the managed tier. - Closing argument: Dries' original 2007 announcement already described Drupal as a place to keep managed content that other tools and websites could access via APIs and access controls. > [!quote] > 19 years later, the other tool might be an AI agent. - Sign-off: "Come for the code, stay for the community," repeated, followed by "I'm Hayden. This is Headless." ## 📚 References The transcript itself contains no links; the video description was not captured with any links either, and the following come from primary sources for named entities. - [Drupal](https://www.drupal.org/) — the open-source CMS project founded by Dries Buytaert, released January 2001 - [Acquia](https://www.acquia.com/) — the commercial company co-founded by Buytaert and Jay Batson in June 2007 - [Dries Buytaert's blog](https://dri.es/) — the primary source for nearly every claim, date, and quote in this video, including the "product we should not have killed" post and the May 2026 reputation-gap post - [Drupal Association](https://www.drupal.org/association) — nonprofit steward of drupal.org, named as the recipient of Acquia's Fair Trade contribution - [Views (Drupal module)](https://www.drupal.org/project/views) — the contributed module the video cites as merging into Drupal 8 core in 2012 - Vista Equity Partners — named as the source of a 2019 majority investment in Acquia; no further detail given - Thomas Skola — named as the source of the "is that still around?" anecdote; spelling and affiliation unverified from this video alone ## 🗣️ Paraphrase - **The hook.** A company that spent years pulling Drupal out of its own branding just bet its AI strategy on putting it back. Why? - **The origin.** A student's message board for friends in 2000 became Drupal in 2001, then a global contributor community with its own con, its own mascot, and a saying that outlasted every rebrand: come for the code, stay for the community. - **The business.** Acquia, founded 2007, was explicitly not supposed to close the open-source project. It was services and support layered on top, first for a curated package, then (2009) for all of Drupal 6 including custom code, because real customer websites are messy. - **The regret.** Drupal Gardens let anyone build a no-code Drupal site; over 100,000 did. Acquia killed it to fund enterprise tools instead, and its founder later called that, in his own published words, the product they should not have killed. - **The messy portfolio.** A run of acquisitions (Mautic, a CDP deal, and a second, confusingly-named "Mautic" deal two years later) built out a marketing-and-content stack around Drupal, with AI already in the announcement language back in 2019. - **The community kept moving.** A community-built module (Views) became part of core. Drupal CMS 1.0 packaged the common assembly work. Drupal Canvas gave content teams a visual page builder. None of this required Acquia at all. - **The perception problem.** Someone at an AI event asked if Drupal is still around. That single anecdote becomes the video's justification for the whole rebrand: the software outran its own reputation. - **The two-tier answer.** Acquia Source splits into a fully managed tier (boundaries: no core changes, no drupal.org modules, but custom components and APIs) and a self-managed tier for teams that need real control. Same CMS, different jobs. - **The AI argument.** Cheaper AI-assisted content production doesn't make governance less important, it makes it more important: who can edit what, what's approved, what changed. Drupal's access-control layer is the thing that makes an AI agent safe to point at a 1,500-post site. - **The money.** 2% of eligible Acquia partner deals fund the Drupal Association, paid from Acquia's margin, not from customers or partners directly. - **The exit.** Customers on the managed tier can export their whole site (code, config, content) and run it elsewhere, a promise made in December 2025. - **The callback.** Buytaert was describing Drupal as structured content plus API access controls back in 2007. Nineteen years later, the thing on the other end of the API might just be an AI agent instead of a website. ## 📰 Newsletter **Acquia spent years quietly de-emphasizing Drupal in its own branding. Then it bet its AI strategy on putting the name back under the logo. The story behind that decision is older than AI, and more interesting than a rebrand deck.** Drupal started in 2000 as a message board for a few students sharing one internet connection in Antwerp. Dries Buytaert released the software in January 2001. Twenty-five years and one saying later, "come for the code, stay for the community" still closes the video. Acquia, founded with Jay Batson in 2007, was explicit from day one about what it was and wasn't: *"Drupal remained the open source project, and Acquia was the business built around helping organizations use it."* Services and support, not a closed fork. **The regret is the most honest thing in the video, and it's sourced to the founder himself.** Drupal Gardens let anyone build a no-code Drupal site. Over 100,000 did. Acquia killed it to fund enterprise features instead, and years later Dries published a post titled, in his own words, about *the product we should not have killed.* That's an unusual thing to admit about your own company's history, and the video leans on it rather than around it. What follows is a run of acquisitions (Mautic for marketing automation in 2019, a customer-data-platform deal, a majority investment from Vista, and a second, confusingly-attributed "Mautic" deal two years later for digital assets) that built Acquia into a full digital experience platform. Meanwhile, and this is the part that matters, the open-source side kept moving on its own schedule: Views merged into Drupal core in 2012, Drupal CMS 1.0 shipped in January 2025, Drupal Canvas gave content teams a visual builder in December 2025. **The pivot of the whole essay is one overheard sentence:** *"Drupal? Is that still around?"* Someone asked that at a Drupal AI event in New York. The video's argument is that the software modernized faster than its reputation, and the rebrand exists to close that specific gap, not to paper over stagnation. Acquia's answer is a genuine two-tier split. Source CMS is fully managed: Acquia runs the Drupal back end, and the customer's team builds inside fixed boundaries, no core changes, no drupal.org contributed modules. Cloud Platform is the self-managed tier for teams that need real control. A university, the video's own example, plausibly needs both at once: a heavily customized main site and a simple alumni page. **The AI argument is the sharpest reasoning in the video.** Dries' own site (1,500+ posts, 10,000+ photos) is the proof point: an AI agent can make edits, but Drupal still holds the content and the access controls, who can edit what, what's approved, what changed between revisions. *"AI makes producing things easier while increasing the importance of managing what gets produced."* That's the actual thesis behind renaming the homepage from "digital experience platform" to "agentic content platform" on September 14, 2026. Two more details are worth remembering. First, the funding commitment is concrete: 2% of eligible Acquia partner deals goes to the Drupal Association, paid from Acquia's margin, not a customer surcharge. Second, the exit path is real, at least as a promise: a managed-tier customer can export a complete Drupal site, code, configuration, and content, and run it somewhere else. That's the thing that makes the managed tier's boundaries tolerable rather than a trap. **And the closing callback earns its place.** Dries' original 2007 startup announcement already described Drupal as a place to keep managed content that other tools and websites could access through APIs and access controls. Nineteen years later, the other tool might just be an AI agent. The mechanism didn't change. What's plugged into it did. The gap in the reasoning: every date and quote in this video traces back to Dries Buytaert's own posts and announcements. No customer, competitor, or analyst appears. And the only brand-name evidence offered for Drupal's continued enterprise relevance, The Economist, the Grammy Awards, whitehouse.gov, is from 2009. Seventeen years before the "still around?" question the video itself raises, and the video never answers it with a comparably recognizable name from this decade. Links: [Drupal](https://www.drupal.org/) · [Acquia](https://www.acquia.com/) · [Dries Buytaert's blog](https://dri.es/) ## ✅ Action items #### DevRel - Developer advocacy: the "is Drupal still around?" gap is a DevRel failure mode with a name. Shipped capability that never reaches the people who formed their opinion years ago is exactly the reputation-lag problem any long-running open-source project's advocacy team should be watching for. - Education: the managed-versus-self-managed distinction (Source CMS's fixed boundaries versus Cloud Platform's full control) needs explicit teaching to buyers before they pick a tier, the same way any two-tier hosting story does. - Developer experience: Drupal CMS 1.0 and Drupal Canvas both reduce the assembly work a beginner has to do before they have a working site. That's the same "shrink the surface area" move DevRel teams push for in other ecosystems. - Developer marketing: the September 14, 2026 rebrand (digital experience platform to agentic content platform) is a live case study in relabeling around new audience expectations without changing the underlying product, worth studying for what it does and doesn't fix. - Community management: "come for the code, stay for the community" as an explicit, repeated recruiting line across 25 years is worth studying directly as a naming choice, not just admiring. - Cross-project: the Drupal Association's 2%-of-margin funding number is a concrete figure that any funding conversation for another advocacy or community function can point to as a real precedent. #### OSPO - Policy & Governance: Source CMS's fixed boundary (no core modification, no drupal.org contributed modules, but custom components and APIs allowed) is a governance tradeoff any OSPO weighing a managed-tier offering for its own project should study directly. - License Compliance: not applicable to this source. - Security Management: an AI agent operating inside a CMS with "human review for higher risk actions" is a new trust boundary, and the video gives no detail on how risk tiers are actually defined or enforced. That gap is exactly what an OSPO reviewing an AI-agent CMS feature needs closed first. - Software Inventory: Acquia's own acquisition history (Mautic, a customer data platform, Source Workspace) shows how a vendor's own portfolio sprawl can outrun its documentation. The two-Mautic-acquisitions confusion in this video is the symptom, not the disease. - Developer Support: not applicable to this source. - Community Engagement: not applicable to this source. - Strategic Alignment: "Drupal remained the open source project, and Acquia was the business built around helping organizations use it," stated at founding in 2007, is a strategic-alignment artifact worth producing in writing for any commercial-open-source project, not just quoting after the fact. #### Community - Maintainers: Views started as a community-maintained contributed module before merging into Drupal 8 core in 2012, a direct, citable precedent for "contributed work earns a path into core." - Contributors: not applicable to this source. - Sponsors: the Drupal Association's Fair Trade initiative (2% of eligible partner deals, funded from Acquia's margin, not a customer surcharge) is a sponsor-funding structure worth evaluating against other communities' models. - Ecosystem: barring drupal.org contributed modules inside the managed Source CMS tier channels demand toward Acquia's own custom-component and API path. That's an ecosystem-shaping decision with real consequences for what gets built and by whom. #### WordPress - Core: the Views-into-core precedent (community module proven out, then merged) mirrors how WordPress Core has absorbed plugin-proven features into the block editor; worth a direct side-by-side write-up. - Core Performance: not applicable to this source. - Core AI: Acquia AI's auth-gated agent permissions with "human review for higher risk actions" is a directly relevant comparator for WordPress's own Core AI discussions about agentic editing, especially on the open question of how risk tiers get defined. - Core Program Team: not applicable to this source. - Mobile: not applicable to this source. - Playground: the site-export portability promise (code, configuration, content, run it elsewhere) is the same proof-of-portability that WordPress Playground already demonstrates; worth a direct comparison of what each actually exports. - Community: both the "come for the code, stay for the community" ethos and the "is that still around?" reputation-lag risk are things WordPress's own community messaging should watch for in itself, not just in Drupal. - Training: the managed-versus-custom split maps onto the same beginner-versus-developer track distinction WordPress Training already has to design for. - Marketing: the September 2026 rebrand is a live case study for how to reposition a platform's brand around new capability without over-claiming; worth a structured teardown. - Support: the fixed boundary on Source CMS (no core mods, no contributed modules) parallels the support boundary managed WordPress hosts draw around plugin access; a direct comparison would be useful. - Design: Drupal Canvas, a visual in-browser page builder shipped December 2025, is a direct feature comparator to the WordPress block editor and Site Editor; worth a capability comparison. - Documentation: not applicable to this source. - Photos: not applicable to this source. - TV: not applicable to this source. - Polyglots: not applicable to this source. - Accessibility: not applicable to this source; no accessibility claims are made about Drupal itself in the video. - Meta: not applicable to this source. - CLI: not applicable to this source. - Hosting: Acquia's two-tier model (Source CMS managed, Cloud Platform self-managed) is structurally the same segmentation a host offering both WordPress and Drupal, including Pantheon, already has to reason about across two different CMS ecosystems. - Tide: not applicable to this source. - Openverse: not applicable to this source. - Themes: not applicable to this source. - Plugins: the restriction against installing drupal.org contributed modules inside the managed tier is structurally the same tradeoff a managed WordPress host's plugin restrictions impose; a direct cross-CMS comparison is worth writing up. #### The WPOCC - Programs: not applicable to this source. - Projects: not applicable to this source. - Funding experiments: the Drupal Association's Fair Trade model, 2% of eligible partner deals funded from Acquia's margin rather than passed to the customer, is a directly comparable funding-experiment structure worth studying against the WPOCC's own funding models. ### FAIR - Technical independence: the site-export portability promise (code, configuration, content, "run it elsewhere," made December 2025) is exactly the kind of exit guarantee a federated or independent infrastructure effort should hold any vendor to, and it's checkable. - Policies and covenants: Acquia's founding-era commitment, stated publicly in 2007, that it would not close-source Drupal, is a real precedent for the kind of written covenant FAIR aims to formalize. - Productized governance artifacts: the Source CMS / Cloud Platform split, with an explicit, stated boundary list (no core modification, no contributed modules, custom components and APIs allowed), is a reusable template for productizing a governance boundary. ## 🧪 Hypotheses - Customers on Acquia's managed Source CMS tier report faster time-to-publish but lower feature-customization satisfaction than customers on Cloud Platform. - Enterprise buyers weighted the December 2025 site-export portability promise as a material factor in choosing the managed tier over a competitor's locked-in managed CMS. - The Drupal Association's Fair Trade funding, drawn from Acquia's margin rather than customer price, produces a measurable funding increase without a corresponding increase in Acquia contract prices. - Organizations using Acquia AI's auth-gated, human-reviewed agent permissions report fewer content-governance incidents than organizations giving AI agents unrestricted CMS access. - Public perception of Drupal's relevance ("is that still around?") lags its actual shipped-feature timeline (Drupal CMS 1.0, Canvas, Source Workspace) by multiple years, measurable as a gap between sentiment trend and release timeline. ## 📊 Methodology - **Tier satisfaction.** Survey Source CMS and Cloud Platform customers matched by organization size and use case on time-to-publish and customization satisfaction; the two tiers being marketed to different needs is a real confound to control for. - **Portability as a purchase driver.** A/B test managed-CMS sales conversations with and without the export-portability guarantee stated up front; measure close rate and stated objection themes. - **Fair Trade funding effect.** Compare Drupal Association funding levels and Acquia contract pricing before and after the initiative's start; the video gives no baseline number, so this starts from zero public data. - **Agent-permission incident rate.** Compare content-governance incidents (unauthorized edits, unapproved publishes) between CMS deployments with tiered agent-review gates and deployments without, matched by content volume. - **Perception-lag measurement.** Track search-interest and sentiment trend for "Drupal" against the dated release timeline in this video (Drupal CMS 1.0, Canvas, Source Workspace, the rebrand); a persistent gap between release dates and sentiment recovery would support the hypothesis. - **Data sources.** Acquia's own release announcements and Dries Buytaert's blog; Drupal Association financial disclosures if published; independent CMS market-share and sentiment trackers. - **Limits.** Every number in the video (100,000+ Gardens sites, 1,500+ posts, 2% Fair Trade contribution) is stated once, by the narrator, sourced to Acquia or Dries directly. None is independently verified in this video, and no comparison figure from a competitor or analyst appears anywhere. ## ❓ Questions - What did the Drupal Association's Fair Trade contribution actually total in its first partial year, and how does Acquia define an "eligible" partner deal? - Which company was actually acquired for "digital assets and product information," and why does the transcript name Mautic for two different deals with two different purposes? - How exactly is a "higher risk action" defined and enforced in Acquia AI's human-review gate, a technical permission model, a workflow checkpoint, or a UI prompt? - Is the December 2025 site-export promise (code, configuration, content) already shipped and testable today, or still a stated intention? - Why does the video's only proof of continued Drupal relevance date to 2009 (The Economist, the Grammys, whitehouse.gov), with no comparably recognizable 2020s example offered? - What is Thomas Skola's actual role and affiliation, and is the "is that still around?" quote independently verifiable outside this video? - How many Source CMS customers eventually migrate to Cloud Platform, or the reverse, and does that migration rate support or undercut the "start managed, grow into control" narrative? ## 🔮 Future research - Comparative study of managed-versus-self-managed CMS and hosting tiers across vendors (Acquia, WordPress VIP, Pantheon) on customer migration patterns between tiers. - Independent, non-vendor-sourced tracking of open-source CMS platform sentiment against actual release cadence, to test whether perception genuinely lags shipped capability the way this video assumes. - Study of margin-funded (versus price-passed-through) commercial-open-source foundation funding models, benchmarked against WordPress's Five for the Future and similar contribution structures. - Technical research into permission and risk-tiering models for AI agents operating inside content-management systems generally, not specific to Drupal. ## 💡 Implications - **Practice.** DevRel and marketing teams evaluating any vendor's "agentic content platform" claim should ask for the underlying permission and review model, not just the feature list, since this video shows how thin that description can be even when the claim is made publicly. - **Policy.** Margin-funded, non-price-passed-through contributions to an open-source foundation (the 2% Fair Trade model) are a concrete, benchmarkable funding structure other foundations and their vendor ecosystems could evaluate. - **Security.** An AI agent with content-editing capability inside a CMS is a new trust boundary. "Human review for higher-risk actions," stated in one sentence with no technical detail, is not yet a threat model. - **Education.** Reputation-lag problems, "is that still around?", need recent, specific proof points to close, not decade-old brand names. A DevRel or marketing team relying on 2009-era case studies to answer a 2026 skepticism question is using the wrong evidence for the question being asked. - **Funding.** Not directly addressed beyond the Fair Trade figure, though the entire narrative's credibility depends on whether that 2%-of-margin commitment is independently verifiable rather than self-reported. ## 🧠 Learning styles assessment - Reading level estimate: roughly Grade 7-8 by the Flesch-Kincaid Grade Level formula. Short, mostly present- and past-tense declarative sentences, minimal jargon until the DXP and AI-agent section, where terms (Source Workspace, contributed modules, digital experience platform) arrive with no definition for a newcomer. #### 👀 Visual learners - Present: the narration is built around concrete, visualizable objects, a folder full of MP3s, a blue mascot, a page builder arranging components, a university with two different sites. - Improve: the transcript alone gives no evidence of on-screen dates, names, or a timeline graphic; a viewer relying only on audio would have to hold nine dated events (2001, 2007, 2009, 2012, 2019, 2021, Jan 2025, Dec 2025, April 2026, Sept 2026) in working memory unaided. #### 🔊 Aural learners - Present: a single, steady narrator voice with no interview cuts, no crosstalk, and a consistent pace throughout. - Improve: no chapter breaks or verbal signposting ("first," "next") mark the shift between the history section and the current-strategy section; the transition happens mid-sentence. #### 🗣️ Verbal learners - Present: strong. The essay is built from stated reasoning ("that's why having both offerings matter") rather than assertion alone, and it names its own uncertainty in places ("the story behind this rebrand started long before anybody was selling AI agents"). - Improve: terms like DXP, CDP, and "contributed modules" accumulate with no gloss for a viewer outside the Drupal ecosystem. #### 🧩 Kinesthetic learners - Present: minimal, evaluable from the transcript alone. No walkthrough of an actual Source CMS or Canvas interface is described in words. - Improve: a viewer wanting to try the two-tier model or the export feature has no stated URL, demo link, or sign-up path anywhere in the narration. #### 🧠 Logical learners - Present: the video's strength. The two-parallel-tracks argument (commercial expansion versus community ease-of-use work) and the closing 2007-callback argument are both structured, evidence-based claims, not assertions of value. - Improve: no independent figure or comparison appears anywhere; every number and date traces to one source (Acquia or Dries Buytaert), which a logical learner would flag immediately as a single-source risk. #### 🧑‍🤝‍🧑 Social learners - Present: the community angle (contributors, meetups, camps, "stay for the community") is treated as a real, ongoing social structure, not decoration. - Improve: no named contributor, community member, or customer appears; the only individual named as a source outside the company is Thomas Skola, in a single secondhand anecdote. #### 🧘‍♀️ Solitary learners - Present: good. The essay is self-contained, chronological, and followable alone with no external context required. - Improve: 14 minutes covering 25 years and roughly nine dated milestones is dense; a solitary learner pausing to verify any single claim would have no citation trail to follow beyond "Dries said." #### 🌿 Naturalistic learners - Present: minimal. No environmental, sustainability, or resource-cost angle is raised anywhere, including around running multiple AI agents inside a CMS at scale. - Improve: the video's own thesis, cheaper AI production, has an unexamined resource-cost dimension that a naturalistic framing would surface and this essay does not. ## 📊 Accessibility assessment #### Screen reader semantics - Present: not evaluable for a video artifact from the transcript alone. - Improve: a structured description with the nine dated milestones and timestamps would let a screen-reader user jump directly to any era of the story instead of scrubbing linear audio. #### Keyboard navigation - Present: inherits YouTube's player. - Improve: no chapters are evident across a 14-minute video that covers at least two distinct registers (25-year history, then current product strategy); chapter markers at the 2019 acquisition run and the 2025-2026 product timeline would meaningfully help. #### Contrast and readability - Present: not evaluable from the transcript alone. - Improve: not evaluable from the transcript alone; a full accessibility pass would need the actual video. #### Text resizing and reflow - Present: not applicable to video content directly. - Improve: applies to any linked blog posts (Dries Buytaert's) the video draws from; not evaluable here. #### Media and captions - Present: auto-generated captions cover the full runtime. - Improve: captions mangle the mascot's name (Druplicon rendered as "the Drupal con") and appear to conflate two different company acquisitions under one name ("Mautic," twice). For a video whose entire value is specific company names, product names, and dates, uncorrected captions materially reduce both usefulness and searchability. #### Forms and interactions - Present: not applicable to this source video. - Improve: not applicable to this source video. #### Standards reference - WCAG 2.2 AA notes: 1.2.2 Captions is met only nominally, with likely errors on load-bearing proper nouns (the mascot name, at least one acquisition target). 2.4.5 Multiple Ways is unmet: no chapters, no transcript link, and no on-screen timeline for a video spanning 25 years of dated events. ## 🌍 DEIB assessment #### Cultural breadth - Present: the origin story is explicitly rooted in Antwerp, Belgium, and the video credits a global volunteer contributor base (translators, documentation writers, meetup organizers) without singling out any one region. - Improve: every named business decision-maker in the video (Dries Buytaert, Jay Batson) and every named customer example (MTV, The Economist, the Grammy Awards, whitehouse.gov, an unnamed university) is US or Western European; no example from outside that axis appears. #### Inclusive language - Present: the language throughout is plain and non-gatekeeping; technical terms (DXP, CDP) are used but not weaponized against a newcomer. - Improve: terms like "contributed modules," "digital experience platform," and "Source Workspace" arrive with zero definition, which functions as a soft gate against anyone outside the Drupal ecosystem. #### Neurodiversity support - Present: a steady, single-narrator pace with no interruptions or crosstalk. - Improve: no chapter breaks or explicit verbal signposting mark the shift from history to current strategy, and 14 minutes covering nine dated milestones with no recap is a dense information load without a pause point. #### Representation - Present: contributors are credited collectively (code, translation, documentation, meetups) rather than erased. - Improve: the only two individuals named with any specificity are Dries Buytaert and Jay Batson, both company founders; no community contributor, customer, or independent voice is named or quoted directly. #### Psychological safety - Present: genuinely strong for a vendor-adjacent video. Dries is quoted, via his own post title, admitting a mistake about his own company's history, and the narrator treats that admission as the interesting part of the story rather than something to gloss over. - Improve: the admission is one sentence in a 14-minute video; it isn't followed by any discussion of what changed in how Acquia weighs enterprise-versus-self-serve tradeoffs since, which would have made the self-criticism actionable rather than just candid. ## ✅ Logical validity #### Strong reasoning - **The parallel-tracks argument (00:06:38-00:07:22).** Premises: Acquia's commercial portfolio expanded; the open community project separately kept shipping (Views into core, Drupal CMS 1.0, Canvas); neither guarantees the other is noticed. Conclusion: the rebrand exists to close a visibility gap, not to cover for stagnation. The argument is structured and each premise has a cited example. - **The two-tier business model argument (00:08:48-00:12:25).** Reasoned from a real organizational need (a university's main site versus its alumni site) rather than asserted as a good idea; the boundary list for Source CMS is stated specifically enough to be checkable. - **The 2007-callback argument (00:13:07-00:13:50).** Uses a real, dated historical claim (Dries describing APIs and access controls in 2007) to argue the current AI-agent pitch is an application of an old mechanism, not a new one. This is the tightest piece of reasoning in the video because it's falsifiable: if the 2007 announcement didn't actually describe APIs and access controls, the argument collapses. #### Fallacies - **Hasty generalization from a single anecdote (00:07:22).** *Location:* "Drupal? Is that still around?" attributed to one overheard comment at one event. *Weakness:* a single secondhand quote is treated as representative of a broad perception problem significant enough to justify a company rebrand. *Fix:* survey or sentiment data across a broader sample would support the claim the anecdote is used to carry. - **Outdated evidence answering a current question (00:03:43).** *Location:* The Economist, the Grammy Awards, and whitehouse.gov, all cited as 2009-era Drupal adoptions, offered as evidence of continued relevance. *Weakness:* the video raises a 2026 skepticism question ("is that still around?") and answers it with evidence from seventeen years earlier, which doesn't actually address whether Drupal is relevant now. *Fix:* a comparably recognizable 2020s adopter would close this gap; none is offered anywhere in the video. - **Single-source reliance treated as established fact (throughout).** *Location:* every date, figure, and quote traces to Dries Buytaert's own posts or Acquia's own announcements, relayed by the narrator with no independent verification. *Weakness:* a company's own account of its own regretted decisions and funding commitments is not neutral, even when it's candid. *Fix:* one independent customer, analyst, or competitor voice would materially change the video's evidentiary weight. - **Unresolved internal contradiction presented without flagging (00:05:53).** *Location:* "Mautic" named as the target of two different acquisitions for two different purposes, two years apart. *Weakness:* this is either a factual error or a genuinely confusing real history, and the video states it flatly with no acknowledgment that it doesn't parse. *Fix:* naming the actual second acquisition, or noting the ambiguity on screen, would have prevented this analysis from having to flag it independently. #### Tone of voice - Measured and narrative rather than promotional in register, closer to a documentary essay than an ad, and it's willing to include one real piece of self-criticism (the Gardens regret) rather than presenting an unbroken success story. The tradeoff is that the entire account is still built from one company's own retrospective framing of its own history, so "measured tone" and "independently verified" are not the same thing here, and the video doesn't distinguish between them. ## 🛡️ DARVO analysis - **Deny:** Not present. The video's one moment of real candor, Dries' own "product we should not have killed" post, is a company admitting a specific mistake rather than denying one. - **Attack:** Not present. No individual, competitor, or critic is named or criticized anywhere in the video; the only tension named is an internal, historical resourcing tradeoff (enterprise versus self-serve), not a conflict with an outside party. - **Reverse victim/offender:** Not present. No accusation is in play anywhere in the transcript, and neither Acquia nor Dries is positioned as having been wronged by anyone. - **Assessment:** DARVO patterns are absent, consistent with the video's register: a retrospective company narrative with one genuine self-criticism, not a defensive or accusatory account. Retained per template requirement; the finding is a clean negative. ## 🎯 Conclusion - **Bottom line.** Acquia's September 14, 2026 rebrand is presented as catching the brand up to product work already shipped between January 2025 and April 2026, not as new positioning invented for the AI moment. The evidence for that claim is real and dated, but it comes entirely from Acquia's and Dries Buytaert's own account. - **The idea worth remembering.** AI making content production cheaper doesn't reduce the value of a system that governs what gets kept, approved, and changed. It raises it. "AI makes producing things easier while increasing the importance of managing what gets produced" is the actual thesis behind the rebrand, not the AI feature list itself. - **The concrete number worth checking.** 2% of eligible Acquia partner deals fund the Drupal Association, from margin, not price. It's specific enough to be verified against Drupal Association disclosures, and it hasn't been in this analysis. - **The gap worth naming.** The video answers a 2026 "is Drupal still relevant?" question with 2009 evidence, and never resolves which company Acquia actually acquired the second time it names "Mautic." Both are checkable, and neither is checked here. - **Practical next step for readers.** Before repeating any date, acquisition name, or funding figure from this video, verify it against Acquia's own public record or Dries Buytaert's blog directly, since the video itself is a secondhand relay of that record, not a primary source. ## 🔄 Refactor Appendix — Are we in Drupal's Renaissance? ### 📚 Literature Atoms (H3) #### [H1] Killing a no-code product for enterprise focus became a named regret > [!quote] > Years later, Dries published a post called the product we should not have killed. **Context & use**: - ~00:04:28, describing Drupal Gardens, a no-code Drupal builder that reached over 100,000 sites before Acquia shut it down to fund enterprise features instead. - A rare instance of a company founder naming his own resourcing decision as a mistake in the title of a public post, not just in retrospective interview softening. **Tags**: #xref #articleseed #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H2] A platform can modernize for years before its reputation catches up > [!quote] > Drupal? Is that still around? **Context & use**: - ~00:07:22, a secondhand anecdote from a Drupal AI event in New York, used as the pivot for the entire rebrand narrative. - The gap between shipped capability and public perception is treated as the actual problem the September 2026 rebrand solves, more than any single feature. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H3] Cheaper AI production raises the value of what governs it > [!quote] > AI makes producing things easier while increasing the importance of managing what gets produced. **Context & use**: - ~00:10:15, Dries' own site (1,500+ posts, 10,000+ photos) as the worked example: an AI agent can edit, but Drupal still holds the access controls and version history. - The actual thesis behind renaming the homepage from "digital experience platform" to "agentic content platform." **Tags**: #xref #articleseed #aphorisms <!-- atomicity: 1 idea ✓ --> #### [H4] Agent permissions inside a CMS need a stated risk-review gate > [!quote] > The company said users could create and manage agents in the browser with permissions and human review for higher risk actions. **Context & use**: - ~00:09:31, describing Acquia AI within the April 2026 Source Workspace announcement. - Stated in one sentence with no technical detail on how "higher risk" is defined; the mechanism is named but not specified. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H5] A vendor can fund its foundation from margin instead of price > [!quote] > 2% of eligible partner deals goes to the association. **Context & use**: - ~00:10:57, the Drupal Association's Fair Trade initiative, funded out of Acquia's margin rather than a customer surcharge or a partner revenue cut. - A concrete, checkable number in a video where almost every other figure is a single-source, unverified claim. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] A regretted resourcing decision outlives the constraint that caused it **Claim** (one sentence, Courtney's voice): When a young company kills a low-friction product to fund an enterprise pivot, the resulting regret gets remembered long after the resource constraint that forced the choice is gone. **Evidence pointer**: [[#H1]] **Scope & conditions**: Holds when the killed segment had a real, sizeable audience (100,000+ sites here) and the company genuinely lacked resources to serve both tiers at once. Breaks down when the cut segment was never viable at any investment level, in which case killing it is a correction, not a resourcing tradeoff. **Links**: - [[A count is only a measurement while the counted thing is costly]] — because contrasts on what "success" looked like for the killed product (adoption, not revenue) - [[Self-selection is what makes an audience worth measuring]] — because applies-in evaluating whether Drupal Gardens' 100,000 sites were the engaged audience worth keeping - [[Alarm fatigue before adding alarms]] — because contrasts on a different kind of decision made under the same resource constraint <!-- atomicity: 1 idea ✓ --> #### [P2] Reputation lags shipped capability, and old proof points don't close the gap **Claim** (one sentence, Courtney's voice): A platform can modernize for years before public perception catches up, and reaching for a decade-old proof point to answer a current skepticism question doesn't close that gap, it exposes it. **Evidence pointer**: [[#H2]] **Scope & conditions**: Holds for any tool or platform with an established, era-specific reputation that the underlying product has since outgrown. Breaks down when the reputation is accurate and current, not lagging, in which case the fix is the product, not the messaging. **Links**: - [[DevRel exists because impersonal channels failed with this audience]] — because extends into why a credible, current voice, not a decade-old brand name, is what actually closes a reputation gap - [[A count is only a measurement while the counted thing is costly]] — because contrasts on what evidence actually changes perception versus what merely restates old facts - [[Counting artifacts stopped being informative when artifacts stopped being expensive]] — because applies-in a parallel case of a metric or proof point outliving the condition that made it meaningful <!-- atomicity: 1 idea ✓ --> #### [P3] Cheap AI production makes governance the scarce resource, not the content **Claim** (one sentence, Courtney's voice): Once AI makes producing content or code cheap, the thing that becomes newly scarce and valuable is the system that governs what gets kept, approved, and changed, not the production itself. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds wherever volume was previously constrained by production cost and that constraint has been removed. Breaks down where governance was already the bottleneck before AI arrived, in which case AI just makes an existing bottleneck more visible rather than newly valuable. **Links**: - [[A count is only a measurement while the counted thing is costly]] — because extends the same shift (cheap output) into what becomes newly scarce (governance, not production) - [[Agent permissions inside a CMS need a stated risk-review gate]] — because evidence-for the mechanism this claim depends on - [[The exposed tool surface can be a function of session state]] — because contrasts on a different axis of AI-agent access control, session state rather than a stated risk tier <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Compare Acquia's Source CMS / Cloud Platform two-tier split directly against how Pantheon structures managed-versus-developer-controlled tiers across WordPress and Drupal #fleeting #inbox - [F2] Check whether Acquia AI's "human review for higher risk actions" has any published technical spec anywhere; the video only gives it one sentence #fleeting #inbox - [F3] Compare the Drupal Association's 2%-of-margin Fair Trade model directly against WordPress's Five for the Future contribution structure #fleeting #inbox - [F4] Verify "Thomas Skola" and the second "Mautic" acquisition before repeating either detail anywhere public #fleeting #inbox - [F5] Read Dries Buytaert's "product we should not have killed" post directly; it's the single most self-critical primary source named in this video #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Read Dries Buytaert's blog post on why Drupal Gardens should not have been killed, before citing Acquia's product history anywhere #things - [ ] Draft the permanent note "Cheap AI production makes governance the scarce resource, not the content" and cross-link it to the WebMCP agent-permissions note from the Storyblok episode #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Are We in Drupal's Renaissance.md|Are We in Drupal's Renaissance? by Hayden (Headless)]] ## Highlights - Years later, Dries published a post called the product we should not have killed. That's a hell of a title to publish about your own company. And I respect it. But his explanation is what makes this story interesting. Enterprise customers needed more, custom integrations, stronger governance, tools for managing whole fleets of websites. Acquia developed that side of the business into Cloud Site Factory. Keeping both paths going stretched the resources of a young company, so it chose enterprise. Dries' regret was the ([View Highlight](https://read.readwise.io/read/01m3m26559c2xg28z21ss2dwhb)) - Note: [H1] Killing a no-code product for enterprise focus became a named regret - Tags: atom/literature/h1 - These were changes to the open-source project available beyond Acquia. So, there are two stories moving in parallel now. Acquia had expanded its commercial product portfolio. The Drupal community had been working to make Drupal easier to use. Neither of these changes guaranteed that somebody who last tried Drupal years ago would ever notice. Drupal? Is that still around? Someone asked that at a Drupal AI event in New York. Thomas Skola recounted overhearing it in New York. Dries shared his post in May 2026. ([View Highlight](https://read.readwise.io/read/01m3m26adqd70t20gc8ahvhkzk)) - Note: [H2] A platform can modernize for years before its reputation catches up - Tags: atom/literature/h2 - brought into a shared working environment. And with Acquia AI, the company said users could create and manage agents in the browser with permissions and human review for higher risk actions. The pitch was expanding from where a team stores its content to how work gets done across it. And in June, Dries laid out the argument behind that bet. For one person making a small site, an AI builder might be enough. He acknowledged that. But generating a new page is different from managing years of ([View Highlight](https://read.readwise.io/read/01m3m26kff7cwkjdr2nxbgtqrg)) - Note: [H4] Agent permissions inside a CMS need a stated risk-review gate - Tags: atom/literature/h3 - existing content used by different people and systems. His own website was the example. More than 1,500 posts and 10,000 photos. He said he used an AI agent to work on it through Drupal. The agent could help make changes. Drupal still held the content and the controls around it. For an organization, those controls include who can edit something, which version has been approved, and what changed between revisions. His argument was that AI makes producing things easier while increasing the ([View Highlight](https://read.readwise.io/read/01m3m26ert55dsjbkrezg2v5z8)) - Note: [H3] Cheaper AI production raises the value of what governs it - Tags: atom/literature/h3 - explanation for the rebrand. Made the company easier to understand with content at the center and Drupal visibly underneath it. The product work preceded the new identity. So did a concrete commitment to the community behind it. Back in June, the Drupal Association described Acquia's fair trade initiative. 2% of eligible partner deals goes to the association. Funded by Acquia, it comes out of Acquia's margin without reducing the partner's revenue or adding a customer surcharge. That helps fund the organization supporting ([View Highlight](https://read.readwise.io/read/01m3m26p5px96f7zvqj4n4qh5g)) - Note: [H5] A vendor can fund its foundation from margin instead of price - Tags: atom/literature/h3