// Key takeaways

Munich AEM Meetup on 1 October 2026: adaptTo() 2026 Recap & Live-Architecting a Chat-Based CMS

Following the adaptTo() 2026 conference in Berlin, AEM Champions Tad Reeves and Roman Mueller made their way to Munich to meet up with fellow AEM Champion Anian Weber and many other AEM developers & architects in the Munich area to continue the conversation.

The meetup, graciously hosted by our friends at Netcentric (thank you Georg!), was in Munich Central Tower: a location with a lovely, panoramic view of Munich, including an absolutely PACKED Oktoberfest just a short walk away.

We discussed our top talks and themes from adaptTo() (the longest-running AEM developer conference, which just celebrated its 15th year), then moved to a "live architecture" session on the best way to structure an agentic chat interface for a content management system.

Meetup Sessions

https://www.youtube.com/watch?v=w3SP1qOsd0o

Chapters:

Recap of adaptTo() 2026

Roman Mueller opened with a recap of adaptTo() 2026 (Berlin, 28–30 September), and the room then dug into the top AEM & Adobe innovations from the conference.

Live Architecture: What Should a Chat-Based CMS Look Like?

At adaptTo(), Natalia Venditto & Sharanya Vinod gave a great talk, Spellforge to Experience Workspace, on how to approach conversational authoring with Adobe's CX Enterprise Coworker. But a chat box isn't the only part of the UI to think with. What elements would an ideal CMS UI have, where you could make possibly-sweeping conversational changes to critical production content?

Tad Reeves in conversation during the hallway track at adaptTo() 2026 in Berlin.

As an ad-hoc technical dream team (and what a project team the all-stars in that room would make!), we kicked around exactly that: live-architecting what a chat-driven Experience Workspace would actually need to be usable without turning the content tree into cat food.

The current Experience Workspace demo chat harness is just a box in the lower-left corner that can talk to the DA MCP (and friends), and it's already enough to make customers nervous. It can modify documents, add blocks, publish, touch indexes, or delete things based on a prompt, and the blast radius is "the entire set of permissions the MCP has" rather than what a sensible author would ever click.

So what SHOULD the UI have? What are the problems, and how might they be solved?

Here's what we live-discussed, and the questions still floating around (ones we really hope CERTAIN FRIENDS AT ADOBE have a look at):

Some of these feel reasonably thought-through already; others are still open questions we were throwing around over pizza. The through-line: a bare chat box is not the product. The product is the combination of chat + constrained skills + visible, reviewable, human-gated change.

Session Resources

The talks, products and docs that came up during the meetup, for anyone who wants to dig further.

// Content & links discussed in the meetup
More info

adaptTo() 2026

CX Enterprise Coworker

Experience Workspace

From the live-architecture session

Browse upcoming AEM GDC events →

Meetup Speakers