AEM Cloud + Adobe Summit 2026: what’s actually changed in your real projects? | Community
Skip to main content
Level 2
May 10, 2026

AEM Cloud + Adobe Summit 2026: what’s actually changed in your real projects?

  • May 10, 2026
  • 1 reply
  • 9 views

Just been going through some of the announcements from Adobe Summit 2026 around AEM as a Cloud Service and wanted to get a real-world pulse from folks actually building on it day to day.
A few things I’ve been thinking about after working on enterprise AEM Cloud implementations:
The Edge Delivery Services push is getting louder but I’m curious how many teams are actually migrating existing Sites implementations versus greenfield only. In practice the replatforming effort is significant and I haven’t seen a clean story for brownfield migrations yet.
Universal Editor is getting a lot of attention but author adoption in enterprise environments has been mixed in my experience. Has anyone actually rolled it out to a large non-technical authoring team and how did that go?
On the pipeline and CI/CD side, Cloud Manager has improved but environment promotion still feels like it needs work especially around content variable management across stages.
Would love to hear from others are these things you’re running into too or is it just specific to larger enterprise setups? And anything from Summit 2026 that genuinely surprised you or changed how you’re approaching a current project?
Not looking for Adobe docs links, already been through those  more curious about what’s actually happening on the ground for people building real things.

1 reply

avesh_narang
Level 4
May 10, 2026

Key observation ​@akhil_merupula  — completely relate to this.

 

From my experience, one approach that has worked well is to keep the core AEM Sites implementation stable and avoid unnecessary churn, while gradually adopting newer capabilities.

Use Edge Delivery Services (EDS) for new experiences, and introduce the Universal Editor selectively for specific use cases rather than doing a blanket rollout.

At the same time, it’s important to invest in stronger content modeling and move toward an API-first architecture .

 

Thanks !