Episode 3 is here: two "Sources", AI coworkers, and Salesforce’s Enterprise Voltron
| submitted by /u/Aggressive_Trip_4872 [link] [comments] |
| submitted by /u/Aggressive_Trip_4872 [link] [comments] |
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?
| Y'all made Ep. 2 so much more than Ep. 1 and I appreciate this community so much! Feedback was heard and incase you didn't want to hear the whole podcast... here is the story about Drupal's AI readiness à la carte! Thank you again [link] [comments] |
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:
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?