Home
AI is the new UI — what does that mean for Drupal Canvas?
If you're following AI trends and building websites, you've probably heard at least one of these more than once lately:
- AI is the new UI
- Drag-and-drop is out. Language is in.
- The UI is about to disappear
These are bold claims and they're no longer just speculation.
Natural language is becoming the dominant interface. You describe what you want, and the system builds it. As some people on the internet call it:
"WYPIWYG": What You Prompt Is What You Get.
Where Drupal Canvas fits in
Drupal Canvas (formerly Experience Builder) is now a reality in Drupal 11, and it represents a serious move toward visual, component-driven creation. That's a meaningful step for the Drupal editorial experience.
But the timing is interesting. Just as Drupal doubles down on visual building, a new category of tools Bolt, Lovable, v0 showed up and proved that for straightforward sites, you can skip the builder entirely. Describe the layout, get the page.
So the question I kept asking myself: is AI a layer on top of tools like Drupal Canvas, or a reason to rethink how we build entirely?
The answer, it turns out, is both.
Two things are happening at once
On one side, AI is being layered onto existing visual builders:
- Drupal Canvas is gaining AI-assisted content editing and layout suggestions
- Builder.io, V0 allows you describe UI using natural language
- Framer, Webflow, and Sanity all have AI-assist features in their editors
On the other side, prompt-to-site tools are bypassing the builder model altogether for simple use cases. The leapfrog did happen, just not for every use case.
Where visual builders still win
This is where it gets interesting for Drupal specifically. Prompt-to-site tools are great at spinning up something fast. They're not great at:
- Governance: who can publish what, with what approval workflow
- Brand consistency: enforcing design tokens and component constraints across a large team
- Editorial workflows: non-developer content teams who need structure, not a blank prompt
These are exactly the things Drupal has always done well. Drupal Canvas isn't competing with Bolt, Lovable, v0, WIX, etc, it's solving a different problem for a different audience.
The real question
The more useful framing isn't "are visual builders dead?" It's: where does a visual interface add value that a prompt can't replace?
For enterprise content management, the answer is clear. Guardrails, permissions, structured content, and editorial UX matter. AI can assist within that system but it doesn't replace the system.
For the Drupal community, that means the opportunity isn't to fight the AI-first trend, but to make Drupal Canvas the best surface for AI-assisted structured content creation. That's a position worth building toward.
I'm curious how others in the Drupal and broader CMS community (Contentful, Sanity, Storyblok) are thinking about this intersection. Are you adding AI on top of your existing tools, or rethinking the workflow from scratch?