I went into this expecting to cover Acquia’s new branding.

I ended up going back to a student in Antwerp trying to help his friends leave messages for each other.

You know how that goes.

Disclaimer: I host r/HeadlessPodcast, and the latest episode follows Drupal’s beginnings, the community, Acquia’s formation, Drupal Gardens, and the path to Source and the new “Powered by Drupal” branding.

The Gardens story really stuck with me. Dries publicly revisiting a product decision and saying they should never have killed it gives this whole thing some weight.

But so does everything the community kept doing in the meantime. Contributors, maintainers, documentation, translations, camps. “Come for the software, stay for the community” earned its place in this episode.

My take is pretty positive. Drupal CMS, Canvas, and the renewed visibility could give people a reason to reconsider software they formed an opinion about years ago.

Video, if you’re interested: https://youtu.be/7ISddVI0SgE?si=W6Josgc2q4Nc0ylx

Ps. For those actually building with Drupal today: what would you show someone whose last experience was five or ten years ago?

the Webflow Source announcement sent me back into Acquia’s Source CMS product guide.

it explicitly says "customers can’t modify the underlying Drupal code or install contributed modules".

I understand the deal: less maintenance responsibility, fewer opportunities to make a beautifully customized disaster.

buttttt Drupal’s flexibility is also why a lot of people chose it.

where does that tradeoff work for you?

for a straightforward marketing site, I can see the appeal. for a project with specific integration or editorial requirements, I’d want to know where the escape hatches are.

what’s the requirement that would make you say “managed SaaS is fine”... or immediately ask for the keys?

I covered the two Sources on my Headless show, but this is the part I’d rather hear from people building and maintaining Drupal sites.

Hey everybody... Webfllow dropped Source by Webflow yesterday and I wanted everyone's first thoughts on trademark rights, and any other thoughts they might have?

Martin Anderson-Clutz at Acquia recently made the case that Drupal is becoming something more specific than a CMS with AI features.

A governed AI harness.

The argument is that Drupal already has most of what agents need:

• Structured content
• Granular permissions
• Editorial workflows
• Revision history
• Centralized governance
• Typed fields and entity relationships
• Canvas AI and the Context Control Center

The funny part is that many of these are the same things that historically made Drupal feel cumbersome to human editors.

The platform famous for asking people to complete seventeen fields may have accidentally spent two decades preparing for robots.

That is legitimately interesting to me.

If an agent is working across hundreds of pages, multiple brands, regulated workflows, and several languages, complexity may stop being baggage.

It may become the safety system.

I covered the argument in the latest episode of Headless:

YouTube
Spotify
Apple Podcasts

Drupal Association article for anyone who wants the source directly:

https://www.drupal.org/about/ai/initiatives/blog/from-headless-cms-to-ai-harness-what-i-took-to-decoupled-days

For people actively building with Drupal AI, does the “AI harness” framing match the reality yet?

Or is the positioning currently ahead of the product?