ÃÛ¶¹ÊÓƵ

What if building modern digital experiences didn’t just get easier, but also more connected, more scalable and more powerful? With the April 2025 release of ÃÛ¶¹ÊÓƵ Experience Manager, we’re introducing a wave of new innovations that does just that. From a sleek new content model admin UI to enhance support for authenticated APIs, smarter form management and a streamlined way to build commerce experiences with edge delivery services, this release is all about giving teams more control, more flexibility and more speed. In this video, we’ll walk through the latest updates that help you manage, build, integrate and optimize with less friction and more impact. Whether you’re a developer, marketer or content strategist, there’s something here for you. Stick around to see how these features are laying the foundation for more intelligent, intent-aware experiences at scale. Delivering intent-aware experiences starts with the ability to generate winning experiences faster and activation puts the content to work. In order to drive intent-aware experiences, optimization needs to happen continuously. Trust and governance is embedded in Experience Manager in every aspect from generation to optimization and foundational services leverage AI to power the broad range of AEM applications. Let’s start with the first group of innovations that unlock better content generation. Let’s start with the content model admin UI. This modernized view of content models is available for creating structured content in AEM. It’s now consistent and integrated with new client-side user interfaces for content fragment management, including search and filtering capabilities. Why does this matter? Because having a unified and intuitive interface for managing content models streamlines the content creation process. You can also extend this functionality with AEM App Builder, making it even more versatile.

Next up, support for authenticated open API based APIs. These new AEM cloud service APIs follow the open API specification, ensuring consistency and reliability. Why is this important? Because well-documented and standardized APIs make integration and development easier. You can browse the technical reference documentation at developer.adobe.com and try out APIs from the convenience of the ÃÛ¶¹ÊÓƵ developer website. Authentication is flexible with options for OAuth server to server credentials or logged in ÃÛ¶¹ÊÓƵ user permissions. Let’s talk about the content fragment launches UI and API. This feature allows for future content authoring and scheduled publishing for headless implementations, similar to code branches in GitHub. Why does this matter? Because it enables more efficient content management and scheduling. You can create a branch, launch, edit future content in the launch, synchronize source changes with the launch using the rebase action, and promote the launch back to the source for publishing or schedule it to automatically promote at a future date.

Next, we have form manager support for edge delivery based forms. Authors can leverage existing form authoring and management interfaces like wizard and form manager to author and update edge delivery services, adaptive forms and fragments. Why is this important? Because it simplifies the form management process and ensures consistency across different delivery platforms. Users can edit and update the adaptive form including submission options using universal editor.

Let’s discuss highlight broken rules on rule editor UI. Form authors can easily identify if any business logic gets broken due to updates in the form, such as updating field names or hierarchical positions. Why does this matter? Because it helps maintain the integrity of business logic and ensures that forms function correctly. Broken rules are clearly indicated with a red dot marker in the form hierarchy and the causal field function is highlighted in red. Users can get details about the cause in a tooltip and can edit update the business logic using rule editor. Okay, so let’s have a look at the features that optimize the experiences for customer and brand. Next up edge delivery services with commerce boilerplate. This boilerplate is a combination of both AEM authoring and commerce storefront removing the need to manually merge both boilerplates.

Why is this important? Because it improves time to value TTV for projects requiring both features. Storefront blocks are extended with configuration to make them editable in AEM universal editor. And there’s an installable content storefront package for AEM author.

Hey guys, this is Martin speaking. In this short video I’m going to talk about the new feature called crosswalk with commerce boilerplate, which we introduced in the AEM cloud service release of April 25. To give you some context, ÃÛ¶¹ÊÓƵ commerce customers that want to build and deploy a storefront on Azure service can use our dedicated commerce boilerplate, which comes with a lot of commerce functionality. Think of all the commerce drop-ins such as PDP, card checkout and so on. This boilerplate supports out of the box document based authoring, so SharePoint and Google Drive. Now we have a lot of joint customers that want to use AEM authoring, also called project crosswalk on top of this commerce boilerplate. And in the past that was a lot of manual work for them to enable crosswalk on top of this boilerplate. So we made it now way easier by introducing a storefront that supports crosswalk and storefront and it’s called AEM boilerplate Xcom here. You can find that pretty easily if you go here on AEM Live, our starting point for Azure service. If you click on build documentation, we have now this new authoring with AEM menu item. If you scroll down to the developer tutorial, then at the beginning you have to select your starting point, your boilerplate starting point. So we have here the traditional boilerplate for crosswalk. So if you build AEM experiences, but if you want to build an ÃÛ¶¹ÊÓƵ commerce storefront experience, then here’s now this new boilerplate. If you go through all the setup steps, what you will create is a storefront on Azure service. And here that’s the storefront boilerplate. And on AEM site, AEM authoring, you deploy the content package, the starter package. So your whole structure of the boilerplate is now available within AEM. And you can now quickly open up here any files. So I’ll pick here the index page. It will open up Universal Editor.

And let’s just say here I want to quickly change here in context the title and will publish the change here directly to Live. Then what you will see here, if I go back to the boilerplate, refresh it, we’ll see the change here. So basically this allows now VisiVic in context authoring capabilities with the full power of AEM authoring on top of every Azure service storefront here within minutes.

Thank you. For more detailed information on the releases we covered today, please see the release notes and consider engaging with us on the AEM community. To recap, the April 2025 release of ÃÛ¶¹ÊÓƵ Experience Manager brings a modernized content model admin UI, support for authenticated open API based APIs, content fragment launches UI and API, form manager support for edge delivery based forms, highlight broken rules on rule editor UI, edge delivery services with commerce boilerplate. These features aren’t just updates, they’re building blocks for delivering intent aware experiences at scale. If you’re ready to take your digital experiences to the next level, check out the release notes and explore these features in Experience League. And if you haven’t already, like, comment and subscribe to stay in the loop on what’s next.

Thanks for watching. We’ll see you in the next release.