I had a long conversation with Dries Buytaert. The parts I think Drupal folks will find most useful:

• He separates "building pages" from "managing content". A five-page site, sure, vibe-code it. Ten editors and thousands of pages across a hundred sites is a different problem, and that one is growing.
• Search engines sent visitors back to the sites that made the content. AI answers don't. He calls it breaking the social contract of the web.
• Tool API and MCP: exposing Drupal's capabilities to agents while keeping permissions and workflows. He thinks agents will generate throwaway UIs for tasks that take 100 clicks today.
• Makers and takers in the AI era, and the $3M/year the Drupal Association spends just on servers.
• A story he hadn't told publicly: the document he had Acquia's early investors sign to protect Drupal.

Full video (71 min, chapters in the youtube video description): https://youtu.be/NiN5ufDJXuo

In this podcast like video, I sat together with Lauri and Balint and talked about Drupal Canvas, from the very beginning, to the strategy, technical details like the data structure, react and astro islands as well as the future of Drupal Canvas.

There are a lot of learnings and insights - not only about Drupal Canvas as a product, but also about how the CMS market will eventually evolve, how AI is changing the way we build products and React coming to the Drupal project.

In this video, I explain the core features of Drupal Canvas including how the UI is structured, how page editing and building works and also showcase how the AI page builder works.

This is a little (actually a big) revolution for Drupal as page building was always a pain point. Drupal Canvas solves that and with the release of version 1 Drupal Canvas, it's ready for production!

Are you already using Drupal Canvas?

I made a video about headless drupal with multisite, site templates and visual editing.

A demo of Drupal/NodeHive service 3 different digital experiences. In this fictional use case, I demo 3 museum digital experience. The main museum website for visitors, a visitor guide for people at the museum itself and an annual report website for other stakeholders.

All content is powered by one Drupal/NodeHive backend. It’s using 3 different site templates with rich editing tools powered by Puck editor.

Drupal, NodeHive and Puck Editor is open source, so you can build this yourself.

We built a simple yet powerful digital asset management system for Drupal/NodeHive. It offers the core functionality of a DAM:

- Quick Mass Uploader
- Fast asset browsing
- Folder Management
- Collection Management
- Zip Export

What do you think?

My session from DrupalCon Vienna is available now and I put out some of my thought.

I still don’t get the point about Drupal CMS because it’s about building a “website” instead of being a content platform for many digital experiences. I get if form small sites - but if you are small you likely already use one of the many SaaS offers.

What do you think?