1. Home
  2. Technical Writing
  3. adaptTo() 2026: 25 talks

adaptTo() 2026 Recap: 25 AEM Conference Talks in 15 Minutes

By Jack Jin · October 10, 2026 · 16 min read · Includes my 14:43 video

adaptTo() 2026 was three days of AEM talks in Berlin, September 28 to 30. I went through all 25 full talks in a 15-minute video: what the talk is, why you should watch it, and my take. This is the written version, in conference order.

adaptTo() 2026 Recap: 25 AEM Conference Talks in 15 Minutes

Recorded October 10, 2026. Each talk below links to its moment in the video, or watch it on YouTube.

adaptTo() 2026, Berlin, September 28 to 30, 2026. Slot times are Berlin time. Each talk links its page and slides on adapt.to.

Why I went through all 25 talks

adaptTo() is Europe's developer conference for Adobe Experience Manager (AEM), organized by diva-e Conclusion. I was just there for the 2026 edition, its 15th anniversary. It was one of the best conferences I've ever attended. Engineers and researchers from Adobe were there, along with engineers and researchers from all over the world. Katie Phillips from Best Buy and I gave a talk there too.

So I gave each of the 25 full talks about 30 seconds on camera. I left out the lightning talks. For each talk I cover three things:

It's meant to help you pick which recordings to watch once they're up. Each take is my own limited understanding from the room. Some of it may be wrong, and a few takes are a little spicy.

Below, every talk has its slot, its speakers, links to its page, slides and moment in the video, and the slide I had on screen while I gave my take.

Day 1: Monday, September 28

talk-01-agents-dont-browse

01Agents don't browse - AEM in the Age of AI

Dominik Steinacher and Carsten Ziegeler, Adobe · Monday 12:30 · Slides (PDF) · Watch at 0:27

Slide titled On the Shoulders of Giants: a CX Coworker Headless box with planning, policing, approvals, sandboxing and memory, next to marketplaces of plugins (skill, API and MCP tools) and context, making scoped calls to AEM product services and third-party services.

Slide: Dominik Steinacher and Carsten Ziegeler, adaptTo() 2026.

What it is

The history behind CX Coworker: what the team didn't like along the way, and how it went from a multi-agent system to more of a mono-agent system.

Why watch

It's one of the better talks on CX Coworker. Highly recommend it.

My take

Moving to a mono-agent is really cool. But parallelism, and capabilities like security per agent, may have changed a little along with it.

talk-02-one-aem-mcp-server

02One AEM MCP Server to Rule Them All

Tanju Erinmez and Jabran Asghar, Adobe · Monday 12:55 · Slides (PDF) · Watch at 1:00

Slide titled What's next?: skills become policies that travel with the token, MCP capability cards in the Adobe Developer Console, AEM MCP governance controls, and an invitation to talk about custom MCP servers behind the AEM MCP server.

Slide: Tanju Erinmez and Jabran Asghar, adaptTo() 2026.

What it is

The story behind the AEM MCP server: the history, the thought process, and how the team solved the challenges of building on MCP servers. MCP, the Model Context Protocol, is the standard way AI assistants call tools in other systems.

Why watch

If you're interested in using the AEM MCP server. The demo is good, too.

My take

It makes sense. MCP is a lot more mature than it was just six months ago, and it was very cool to hear the engineers talk about it.

talk-03-rolling-out-mcp-on-aem

03Rolling Out MCP on AEM: Lessons from Early Production

Divanshu Goyal (TechX) and Pranay Rajput (Pitney Bowes) · Monday 13:30 · Slides (PDF) · Watch at 1:26

Slide titled Blast Radius, not access control: permissions decide what a person is authorized to do, and the server split decides what a machine is even capable of attempting.

Slide: Divanshu Goyal and Pranay Rajput, adaptTo() 2026.

What it is

Real production lessons from rolling out MCP on AEM, from two of my fellow AEM Champions.

Why watch

If you're going to use AEM MCP servers in production. The memes were on point, too. I learned quite a bit.

My take

One capability we could add is some kind of judgment step, with its own tools, that pre-filters before anything reaches the MCP server.

talk-04-aem-elasticity

04Advancing AEM Elasticity: Earlier Signals, Faster Readiness, Better Resilience

Tudor Rogoz and Dominik Süß, Adobe · Monday 14:25 · Slides (PDF) · Watch at 1:56

Slide titled Why Signal Quality Matters: use signals independent of request size, namely absolute CPU usage, server load ratio, response time P95 and queue depth.

Slide: Tudor Rogoz and Dominik Süß, adaptTo() 2026.

What it is

How the people who run infrastructure for many, many customers keep it stable. Most of us haven't thought about that side.

From the talk's slides: the same 600m of real CPU load scales out with a 500m CPU request and stops scaling with a 1000m one, so the talk moves to signals that don't depend on the request size, like absolute CPU usage and queue depth.

Why watch

They go through the science behind site reliability.

My take

I've personally never seen site reliability explained this way. Highly recommend it.

talk-05-securing-aem-customer-code

05Securing AEM Customer Code: Automated fixes for vulnerabilities in dependencies

Andrés Bott and Ramon Bißwanger, Adobe · Monday 15:00 · Slides (PDF) · Watch at 2:21

Slide titled Security: AI landscape: vulnerabilities identified and exploited faster than ever, about 2.3 years in 2018 and hours in 2026, next to a falling line chart from zerodayclock.com.

Slide: Andrés Bott and Ramon Bißwanger, adaptTo() 2026.

What it is

A similar problem to the last talk. AEM as a Cloud Service and Adobe Managed Services have a lot of different customers, with different code quality and different requirements, and this team has to look after all of it. The talk is about fixing vulnerabilities in customers' dependencies automatically.

From the talk's slides: vulnerabilities are identified and exploited faster than ever: about 2.3 years in 2018, hours in 2026.

Why watch

They have a very, very tough job, and it's very interesting to see the techniques they use to solve it.

My take

This was one of the talks without a ton of AI on top of AI, which is great. It's good to see some non-AI talks.

talk-06-aem-content-requests

06AEM Content Requests - Reduce, Reduce, Reduce!

Damian Langsweirdt, Adobe · Monday 15:40 · Slides (PDF) · Watch at 2:54

Slide titled Real results from a customer: 80%+ reduction over 3 iterations, above a bar chart of daily content requests by type that drops over time.

Slide: Damian Langsweirdt, adaptTo() 2026.

What it is

How Adobe licenses AEM as a Cloud Service and Edge Delivery Services (EDS), why content requests matter, and tips and tricks to reduce them.

From the talk's slides: one customer cut content requests by more than 80% over three iterations.

Why watch

To cut your AEM licensing cost.

My take

It's extremely helpful for that. Still, licensing models could maybe be done slightly differently.

talk-07-develop-faster-aem-ai-tooling

07Develop Faster with AEM AI Tooling

Abhishek Garg, Adobe · Monday 17:30 · Slides (PDF) · Watch at 3:30

Slide titled Confidently wrong: an AI-generated Dispatcher filter with /smartCache and /autoInvalidate properties, stamped WRONG, next to the words Fluent. Confident. Not real. The caption says those filter properties don't exist.

Slide: Abhishek Garg, adaptTo() 2026.

What it is

AI tooling for AEM development.

From the talk's slides: left on its own, AI writes a fluent, confident Dispatcher filter with /smartCache and /autoInvalidate properties that don't exist. The tooling lets it see your running instance instead of guessing.

Why watch

It covers all parts of AEM development, including the Dispatcher.

My take

The Dispatcher has always needed a lot of expertise. If you've worked on it, you know. On a first project, it's fairly difficult. Very cool talk.

talk-08-migrate-to-aem-cloud-service-faster

08Migrate to AEM Cloud Service Faster - An Agentic Workflow with MCP and Adobe Migration Skills

Himani Chauhan and Bharat Wadhwa, Adobe · Monday 18:05 · Slides (PDF) · Watch at 3:54

Slide titled The cost of migrating: how long does an AEM migration really take? Months from start to cutover, 8,000+ findings in one BPA report, and about 30% less time to cutover once automated, 6 months manual versus about 4.2 months with Adobe Skills.

Slide: Himani Chauhan and Bharat Wadhwa, adaptTo() 2026.

What it is

How to use AEM tools, skills and MCP servers to get a lot of a Cloud Service migration done. Skills are packaged instructions an AI agent loads for one kind of job.

Why watch

If you're going to go through an AEM as a Cloud Service migration.

My take

They cover both skills and MCP servers, and how to get the work done with them. Very good talk.

talk-09-comparador

09Comparador - Spot the Difference: Surviving AEM Migrations & Deployments Without Going Blind

Krystian Panek and Tomasz Sobczyk · Monday 18:40 · Slides (PDF) · Watch at 4:19

Slide titled The solution: Comparador, a freeware Chrome extension for Chromium, Edge, Brave, Opera and Vivaldi, with screenshots and a list of features: under a minute to install, visual diffing, HTML source diffing, HTTP headers comparison, console logs diffing, metrics comparison and shareable project setups.

Slide: Krystian Panek and Tomasz Sobczyk, adaptTo() 2026.

What it is

A creative way to detect what changed between your current website and the new one you're building, with a Chrome extension.

From the talk's slides: it compares the visuals, the HTML source, the HTTP headers and the console logs, and it installs in under a minute.

Why watch

It was one of the more fun ones, and they got the audience engaged. If you've ever needed to spot the difference between two versions of a site, this is a very creative solution.

My take

It's open source, and I always like open source stuff. A good talk. The two of them did a great job.

Day 2: Tuesday, September 29

talk-10-ai-agent-driven-content-migration

10AI Agent-Driven Content Migration for Edge Delivery Services

Jack Jin (Accenture) and Katie Phillips (Best Buy) · Tuesday 09:00 · Slides (PDF) · Watch at 4:43

Slide titled Conceptually: One Framework, Any Content Process: any trigger (human UI, deterministic, AI trigger) flows through a migrator, an eval step, an orchestrator, a generator and a human step to human oversight, preview publish and final publish, with human governance on the entire flow.

Slide: Jack Jin and Katie Phillips, adaptTo() 2026.

What it is

Our talk, Katie Phillips from Best Buy and me, the first talk of the second day: AI agents that migrate content to Edge Delivery Services.

From our slides: one framework for any content process, with any trigger, any route through the agents, and four places a human can step in.

Why watch

I'd recommend it once the recordings are out.

My take

Three things I'd call out:

  • Like most talks at the conference, ours is very agentic. It's also AI using AI, where most of the other talks were about humans using AI.
  • We think about evals.
  • It's a multi-step process, and the AI agents share a common working process.

That fits content migration well, because you want to run things in parallel. Sometimes you spin up tens or hundreds of agents to migrate a bunch of pages, run evals, throw the results away and do it again. AI using AI can do that in a very scalable way.

talk-11-hybrid-aem-architecture

11Hybrid AEM Architecture: Bridging Server-Side Rendering with Headless React at the Component Level

Shashi Kumar and Daniel Jebaraj, Calix · Tuesday 09:35 · Slides (PDF) · Watch at 5:40

Slide titled Calix Web Platform - Evolution: three screenshots, Calix.com rebuilt in 2024, MyCalix as it was until 2025, and MyCalix refreshed in 2026.

Slide: Shashi Kumar and Daniel Jebaraj, adaptTo() 2026.

What it is

Server-side rendering and headless React combined at the component level in AEM, and how the team solved a lot of the challenges along the way.

From the talk's slides: Calix.com moved onto AEM as a Cloud Service in 2024. In 2026 the MyCalix customer portal got the same components, plus features the HTL components couldn't carry.

Why watch

Watch it if you run a React or Angular website inside AEM as a Cloud Service.

My take

I've seen this done many ways, and this is one of the fairly clean ones. It's a very solid pattern.

talk-12-tales-from-migration-trenches

12Tales from the AEM Migration Trenches

David Catalan and Karl Pauls, Adobe · Tuesday 10:25 · Slides (PDF) · Watch at 6:07

Slide with four labels, AI Cloud Workers, Skills, Harnesses and Models (LLMs), around a small S, A, H, M badge, above three screenshots of migrated websites.

Slide: David Catalan and Karl Pauls, adaptTo() 2026.

What it is

The story of how AEM migrations used to be, starting about two years ago, and how the work moved to a very AI-native way, with AI in the cloud doing a lot of it.

From the talk's slides: the story starts with their first LLM on July 18, 2024 and gets to a one-click Chrome extension backed by an agent on Cloudflare Workers.

Why watch

The storytelling, with animations, from beginning to end.

My take

I enjoyed this one quite a bit. Very cool storytelling.

talk-13-spiritually-succeeding-aem

13Spiritually-Succeeding AEM: Advanced Author Customization in DA

Laurel Timko (JMP Statistical Discovery) and Tad Reeves (Arbory Digital) · Tuesday 11:00 · Slides (PDF) · Watch at 6:43

Slide titled The Anatomy of a Plugin: a short tools/plugin/index.js that reads the page context, calls an API and writes back into the document, a da.live config table that registers it, and a note that about 15 lines of JavaScript plus a simple HTML file make a complete plugin, served from the same repo as the site.

Slide: Laurel Timko and Tad Reeves, adaptTo() 2026.

What it is

The power of plugins in DA, Document Authoring (da.live), told alongside the history of AEM's evolution. The title slide ends with "in Experience Workspace", which is how I introduced it in the video.

From the talk's slides: about 15 lines of JavaScript and a simple HTML file make a complete plugin, served from the same repo as the site, with no separate deploy.

Why watch

It's very grounded in what a plugin can actually do, and the team did a really great job showing it.

My take

I liked this one quite a bit. It reminds all of us how much JavaScript in a browser can achieve.

talk-14-spellforge-to-experience-workspace

14Spellforge to Experience Workspace: Building a Skill-Driven Agent System for DA/AEM

Natalia Venditto and Sharanya Vinod, Adobe · Tuesday 11:35 · Slides (PDF) · Watch at 7:13

Slide titled Bring It Inside: before, authors use a separate AI agent outside the authoring experience; after, AI becomes part of the authoring experience in da.live.

Slide: Natalia Venditto and Sharanya Vinod, adaptTo() 2026.

What it is

How Experience Workspace and da.live came to be, what they can do, and how AI works on top of da.live, with a demo.

From the talk's slides: authors used to work with a separate agent outside the authoring experience. Now AI is part of it.

Why watch

The demo is great. I kind of wish this talk had gone before ours, since our talk was built on Experience Workspace too.

My take

da.live, with its HTML data structure, is very AI friendly. I'm sure Experience Workspace does amazing things with it. Highly recommend it.

talk-15-brand-visibility-in-llms

15Measuring the Unmeasurable: Pre/Post Experimentation for Brand Visibility in LLMs

Nitin Gupta, Adobe · Tuesday 13:30 · Slides (PDF) · Watch at 7:47

Slide titled Finding the right pages: automated scoring: citabilityScore (content gain from optimization) and agenticTraffic (existing AI-crawler traffic) combine into an automated signal that selects pages for experimentation.

Slide: Nitin Gupta, adaptTo() 2026.

What it is

Before-and-after experiments that measure how visible a brand is in large language models (LLMs), the models behind AI chat answers.

From the talk's slides: two scores, citabilityScore (content gain from optimization) and agenticTraffic (existing AI-crawler traffic), combine into one automated signal for which pages are worth fixing.

Why watch

If you care about LLM visibility. All of us do.

My take

This is an area I still need to brush up on, so I was drinking from a fire hose. A very cool presentation.

talk-16-content-supply-chain

16Building an Efficient Content Supply Chain for the AI Era

Istvan Krajnek and Veselin Petrov · Tuesday 14:05 · Slides (PDF) · Watch at 8:10

Slide titled The problem in plain words: a website visit, a customer record and a browsing history that are not connected, a Tuesday to Thursday timeline where the marketing email goes out after the customer bought elsewhere, and four questions nobody can answer in time: identity, intent, action and delivery.

Slide: Istvan Krajnek and Veselin Petrov, adaptTo() 2026.

What it is

Content supply chain and AEM Assets in the age of AI, and how we should think about it. It was one of the few talks at the conference on this topic.

From the talk's slides: a visitor's website session, customer record and browsing history aren't connected, so the marketing email goes out on Thursday, after he already bought the jacket elsewhere.

Why watch

It has a realistic demo of a content supply chain in the modern world.

My take

I really enjoyed it, especially how it focuses more on AEM and less on Workfront. The demo is quite cool too.

talk-17-shifting-the-search-paradigm

17Shifting the Search Paradigm

Mohit Kataria and Bianca Necula, Adobe · Tuesday 14:55 · Slides (PDF) · Watch at 8:35

Slide titled 2026 Evolution, Ease and Practicality: MCP on top of keyword, semantic, hybrid, prefix, multifield, generative and natural language search, aggregates and analyzers, on an indexing and retrieval engine fed by acquisition, custom and AEM content sources.

Slide: Mohit Kataria and Bianca Necula, adaptTo() 2026.

What it is

Adobe investing in search for AEM.

From the talk's slides: it started in 2025 as the Content AI MVP, with keyword, semantic, hybrid and generative search, and added MCP and natural language search in 2026.

Why watch

On AEM projects, I've usually recommended other search engines. With this, AEM projects could use Adobe's own search.

My take

I've always thought this was super exciting. It makes a ton of sense. Maybe Experience League can move over too, since I think it runs on a non-Adobe search engine today.

talk-18-continuous-materialization

18From Cache Invalidation to Continuous Materialization

Marek Czajkowski and Paweł Sobolewski · Tuesday 15:20 · Slides (PDF) · Watch at 9:07

Slide titled When the content changes: Correctness. An edited promo teaser experience fragment is used on /home, /products, /sale and hundreds more pages. The cache key is the URL and the invalidation key is the path, but the real dependency is a graph. The safe fallback, a full-site purge, throws every good entry away to catch the stale ones: manual, error-prone and hard to reproduce.

Slide: Marek Czajkowski and Paweł Sobolewski, adaptTo() 2026.

What it is

The last talk on Tuesday. It goes deep on one niche problem, cache invalidation, shows its core challenges, and moves to continuous materialization.

From the talk's slides: the cache key is the URL and the invalidation key is the path, but the real dependency is a graph. So the safe fallback is a full-site purge.

Why watch

If you're looking into caching and want a really good caching solution.

My take

I always enjoy talks like this. This work needs a lot of rigor, and most architects and teams don't have the time or the patience to do it. Really cool to see it done.

Day 3: Wednesday, September 30

talk-19-aem-forms-rule-authoring

19Reimagining AEM Forms Rule Authoring with Coding Agents

Navneet Agarwal and Ravisanker E, Adobe · Wednesday 09:00 · Slides (PDF) · Watch at 9:38

Slide titled Visual Rule Editor: no-code visual authoring, predefined rule types (When, Show, Set Value Of, Validate), managing and reusing rules, and drag and drop building.

Slide: Navneet Agarwal and Ravisanker E, adaptTo() 2026.

What it is

The first talk of the third and final day: coding agents, skills and an MCP connection that help you write AEM Forms rules.

Why watch

If you use AEM Forms.

My take

AEM Forms is very powerful. Configuring forms by hand takes quite a bit of expertise, and the rule editor is so powerful that it can be hard to configure. An MCP connection on top of all that is very, very cool.

talk-20-tracking-through-the-transition

20Tracking Through the Transition: A Flexible Tracking Architecture for AEM Migrations

Janic Wyslich and Martin Schröter · Wednesday 09:35 · Slides (PDF) · Watch at 10:15

Slide titled Migrate in parallel: two website platforms, one tracking contract. FirstSpirit legacy pages and migrated Adobe AEM pages each have a data layer service feeding one adobeDataLayer, then the acdl_helper and xdmtracker plugin, a datastream, and Adobe Analytics with comparable events across both platforms.

Slide: Janic Wyslich and Martin Schröter, adaptTo() 2026.

What it is

The data layer and analytics through an AEM migration, and the team's migration process.

From the talk's slides: two website platforms, one tracking contract.

Why watch

The data layer, and how data actually gets to Adobe Experience Platform (AEP), Customer Journey Analytics (CJA) or even Adobe Analytics, is constantly underestimated or misunderstood.

My take

A data layer is always good. On Edge Delivery Services we're still choosing the Adobe Client Data Layer, so all of this still applies. The talk also has one of the better diagrams, the one shown here. I may even have reused it in a proposal. I always like good technical diagrams. Great job by the team.

talk-21-index-optimizer

21Stop Messing with Index Definitions: Index Optimizer and Simplified Index Management in AEM

Paul Chibulcuteanu and Benjamin Habegger, Adobe · Wednesday 10:00 · Slides (PDF) · Watch at 11:05

Slide titled Simplified Index Management: a NEW badge on index.diff with customizations, the same for Quickstart.

Slide: Paul Chibulcuteanu and Benjamin Habegger, adaptTo() 2026.

What it is

Adobe's engineering investment in AEM indexing: an Index Optimizer and simplified index management.

From the talk's slides: customizing an index used to mean copying and renaming definitions like damAsset-12-custom-1. Now a customization is a diff: 10 lines of JSON instead of 400 lines of XML.

Why watch

A must-watch if you deal with indexing.

My take

Indexing has always been a fun thing. I personally stopped worrying about it much once the aggregate index got really good. Still, this is a really thoughtful piece of engineering. For those of us who've been in AEM for 15 years, it's evolutionarily ahead of where indexing has been. Super cool.

talk-22-project-asset-hub

22Project Asset Hub - Modernizing AEM Asset Share with Edge Delivery Services, Content Hub, and Edge Compute

Alexander Klimetschek, Adobe · Wednesday 10:50 · Slides (PDF) · Watch at 11:44

Architecture slide: an Asset Portal UI as the custom frontend, an edge worker and storage on an Adobe-managed edge platform (Cloudflare, Fastly) with identity providers and third-party systems, Edge Delivery Services and Content Hub APIs for delivery, and document authoring and AEM Assets author underneath.

Slide: Alexander Klimetschek, adaptTo() 2026.

What it is

Asset Hub: an asset portal coded on Edge Delivery Services that works with Content Hub, running on an Adobe-managed edge.

Why watch

It's a really good use of Edge Delivery Services plus AEM Assets. It also sounds proven, with a ton of users. The talk's slides say one pilot customer has been live since March 2026, with two more in progress and 8,000+ users.

My take

This one was extremely exciting for me. I love Adobe's products. I love Content Hub. But the licensing and IMS, Adobe's identity system, are a bit of a pain, because you have to onboard people into IMS. Now there's an Asset Hub coded on Edge Delivery Services, which is amazing. Why haven't I thought of this? I wish I had, sooner.

talk-23-editorial-ai-in-aem

23Editorial AI in AEM: Giving Editors Control Over LLM-Generated Image Descriptions

José María Franco Fraiz, Cognizant Netcentric · Wednesday 11:25 · Slides (PDF) · Watch at 12:26

Slide titled Prompt anatomy: a minimal e-commerce prompt example that asks for concise, accurate alt text for consumer goods images, with links to fuller versions of the prompts.

Slide: José María Franco Fraiz, adaptTo() 2026.

What it is

AI prompts that generate image descriptions for assets in AEM, with editors in control.

From the talk's slides: they needed a prompt per purpose and per brand, market and language, with marketers managing their own prompts, with real governance, in a UI they already know.

Why watch

If you want a more automated, AEM-native process that generates this for you.

My take

What's unique is that it uses more of the classic Java integrations, and it keeps the instructions for the AI inside AEM, so authors can configure them. I thought that was really interesting. A very cool implementation.

talk-24-15-years-of-women

2415 Years of Women at adaptTo() - The Facts and the Untold Stories Behind the Numbers

Alina Rublea and Angela Schreiber, Adobe · Wednesday 13:30 · Slides (PDF) · Watch at 13:03

Slide titled This is the room today: a photo of the adaptTo() 2026 audience in the conference hall, credited to Marta Cukierman, with the line: Something has shifted. Slowly, but significantly. And we are glad to be back.

Slide: Alina Rublea and Angela Schreiber, adaptTo() 2026. Photo on the slide: Marta Cukierman.

What it is

The facts and the stories behind women at adaptTo() over 15 years. Fifteen years ago there were maybe one or zero women in the room. Over time, more and more came to the conference.

Why watch

A very cool narrative.

My take

Super agree. Diversity is super important, and I'm happy it's more diverse now. In the photo of the room today I can see myself, and my speaking partner Katie from Best Buy. It looks like Lisa Brown, who gave the next talk, had stepped out, but she sat there too. Very cool to see more women in the room.

talk-25-dam-breakfast

25Make Your Own DAM Breakfast with Adobe Experience Manager

Lisa Brown, Accenture · Wednesday 13:55 · Slides (PDF) · Watch at 13:37

Slide titled Demo Journey: The Full Pancake Stack, a six-step wheel. Maude takes your order, the order becomes real (checkout against Magento over GraphQL), Stardust draws your pancakes, AWS IoT Core wakes the kitchen, Make catches the ticket, and you enjoy pancakes.

Slide: Lisa Brown, adaptTo() 2026.

What it is

The last full talk, from my Accenture peer Lisa Brown. She tied AEM to Adobe Commerce, many other integrations and robotics: an AI chatbot takes your order, then pancakes get made on stage.

From the talk's slides: the order checks out against Magento over GraphQL, a custom prompt becomes a pancake design inside locked constraints, and AWS IoT Core sends the design to a PancakeBot as G-code.

Why watch

If you want to see something fairly cool and new: AEM, Commerce, pancake making, robotics and AI all working together.

My take

An extremely ambitious project. Extremely cool talk.

Thanks to the speakers and the organizers

If you made it this far, thank you. And thank you to all the speakers, and to diva-e Conclusion for organizing adaptTo().

The official talk videos should be on the adapt.to schedule in the next week or so. If you'd rather watch than read, the video at the top covers all 25 in under 15 minutes.