Hey everyone,

I was recently looking into better ways to handle theme configurations without having to hardcode everything or constantly hit refresh, and I stumbled on this walkthrough for Space DS 2.x (Space Design System).

It looks like they’ve added a really smooth live preview directly in the admin panel. You can toggle dark/light mode, swap device views, and tweak typography/colors with real-time updates—no saving and reloading required.

A huge plus for me is that it has native Storybook integration for SDC (Single Directory Components). I know getting Storybook to play nice can sometimes be a headache, but the props and dynamic slots seem to map over perfectly here. They also showed off their Lighthouse scores in the video and it's pulling a 99 on mobile, which is pretty sweet.

Anyway, I thought it was a really neat approach to bridging the gap between the admin UI and the frontend. Figured some of you might find it useful if you're building out landing pages or managing complex themes.

Here’s the walkthrough if you want to see the UI in action: YouTube Video Link

Has anyone used this (or a similar setup) in a production environment yet? Curious to hear how it scales!

[not a promotion] One of the developers on our team just wrapped up a deep-dive webinar on how we’re using the ECA (Event - Condition - Action) module alongside Drupal's new AI features.

If you've ever felt like you're writing too much custom code for simple entity triggers or workflow logic, this is definitely worth a look. The session walks through how to build visual automation models that can trigger AI actions (like auto-tagging or content analysis) without touching a custom module.

Check out the full session here: https://youtu.be/uSEYJ5TiCcE

We’ve been moving more of our production logic over to ECA lately to keep things maintainable. Curious to hear if anyone else is using ECA + AI in their current projects, or if you’re still sticking to custom hooks for complex logic?

I’ve been messing around with the new Drupal Canvas AI sub-module, but honestly, the layout output was driving me crazy. It felt like it was just guessing where things should go and ignoring my design system.

I just stumbled on this step-by-step video that explains the "Context" side of things. It shows how to actually train the AI using a coding agent to generate knowledge guidelines so it respects your component props and grids.

If you’ve been struggling with messy AI-generated pages in Drupal, this workflow is a game-changer:

It’s a quick watch but the part about the AI Context module saved me hours of manual tweaking.

We've been working on Aeldris — an AI platform that lets organizations build custom AI assistants trained on their own internal data (PDFs, docs, chats, links, etc.).

Unlike generic chatbots, it uses semantic search agents to understand user intent, so it can handle things like customer service, HR queries, and compliance — without relying on keyword matching.

Drupal powers the content and data layer underneath. Dropped a short demo video if anyone's curious how it all comes together.

Happy to answer questions about the stack or how we approached it.