If there's one thing most of us in the Drupal community can agree on right now, it's that everybody is building pages differently. Some teams are still deep into Paragraphs because the guardrails work. Others moved to Layout Builder to give editors more control over layout. Canvas is picking up real momentum, and it's all over the program at DrupalCon Rotterdam this week. And a lot of teams, especially on decoupled projects, have ended up building their own thing because preview and visual editing had to be solved on the frontend anyway. I don't think that's a bad sign. It tells me the community is still figuring out what the right authoring experience looks like, and the best answers are coming from real projects, not from any single approach. So while DrupalCon has everyone talking about this, I'd like to hear what your team is actually doing: How are you building Drupal pages today? Paragraphs, Layout Builder, Canvas, or something custom? If Canvas is running in production for you, what's working and where are you hitting friction? On decoupled projects, how are you handling visual editing and preview? What did you end up building yourself? If you could design the Drupal authoring experience from scratch, what would it look like? Whether you're in Rotterdam this week or following along from home, I'd love to hear how your team is approaching this. Real project experience is what makes these conversations useful. I wrote more about where I think this is heading here: jmolivas.com/what-should-dru…

If your team uses AI to generate front-end code, you should know what it's actually doing to your organization’s accessibility posture. The three slides in this post show the most common accessibility failures we're seeing in AI-generated code: • Alt text that exists but is inaccurate. • ARIA attributes applied without context. • Building interactions that work with a mouse but break with a keyboard.

The DrupalCon gala was something else. Celebrating 25 years of Drupal surrounded by people who actually made those 25 years happen. That was something. Best part was catching up with Raul Solano, Alain Martínez, and Ronald Aguilar. We've known each other for years through this community. Different companies, different countries, but always crossing paths at these events. Those are the relationships that make open source worth it. I've been around Drupal long enough to see it evolve in ways none of us expected. And being in that room, you could feel there's still a lot left to build. Happy 25, Drupal, and cheers to everyone who's been part of this! #DrupalCon #DrupalConChicago

I'm at DrupalCon Chicago this week. Always good to catch up with familiar faces and have those conversations that only happen in person. We've been putting a lot of work into Drupal Decoupled over the past months, and I'm excited to show where the project is. But I also want to hear what you're building and what challenges you're running into. If you're here, DM me or come say hi between sessions! #DrupalConChicago #DrupalCon

Every time someone tells me decoupled Drupal means losing previews, a painful setup, or giving up the features that make Drupal useful. I want to show them this demo. So that's exactly what we did. We recorded a full live walkthrough of Drupal Decoupled. One-click cloud deployment to a working local environment, editing content, reordering components, submitting forms, all in real time. Instead of explaining why these misconceptions are wrong, we just built it in front of the camera. Every feature people assume you lose when you decouple is right there working. We also cover what's coming next, including Canvas drag-and-drop support and new framework starters. If your team wants a modern front end without giving up the structured content, workflows, and editorial tools that your clients and teams actually depend on, this is worth 30 minutes of your time. We'll be at DrupalCon Chicago next week. If you want to see this live or just want to say hi, come find us. Sign up here: octahedroid.com/webinars/dru…

"Content editors will hate it." "You lose all the Drupal features." "It's too complex to set up." We've heard every reason why teams avoid decoupling Drupal. So instead of talking about it again, we decided to just show it. In our latest webinar, @omers and I do a live demo of Drupal Decoupled: from a one-click cloud deployment on Tugboat to a full local setup on your machine. The whole thing is the actual workflow running in real time. Here's what we cover: • One-click deployment with Tugboat. • Storybook integration for standalone component development. • Live content editing with iframe preview: edit, reorder, preview, and publish. • Webform integration so your forms still connect to Mailchimp, your CRM, etc. • Full local setup with DDEV, Drupal 11, Next.js 16, Tailwind 4, and shadcn Base UI. If you've been on the fence about decoupled Drupal, this is the fastest way to see what it actually looks like in practice. We'll also be at DrupalCon Chicago next week. If you want to see this running live or just want to talk more, come say hi! Sign up for the demo here: octahedroid.com/webinars/dru…