Got some help from my Adobe friends and was able to resolve this: Due to a bug in AEMaaCS 2025.5, the Universal Editor was temporarily disabled and under a feature flag After Adobe set the feature flag, I had to provide the following config to get it working: org.apache.sling.engine.impl.SlingMainSe...

In the first part of our test automation blog series, we explored why test automation is essential for AEM as a Cloud Service (AEMaaCS), where continuous delivery and shared code ownership simply make manual testing inefficient. We covered the four pillars of a robust testing strategy:  Unit tests ...

AEM as a Cloud Service (AEMaaCS) shifts Adobe Experience Manager from a release-based model to a continuously delivered, cloud-native platform. Manual testing simply can't keep up with the pace of deployments, so test automation is now even more important to ensure quality, performance, and stabilit...

Update: There seems to be an OOTB OSGi service called "Universal Editor URL Service", which I configured according to the documentation [1], but it's still NOT opening the page in Universal Editor. [1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/d...

Hi @SapnaTanwar, here are my thoughts: 1. Officially, Adobe supports Universal Editor only with EDS or Headless setups. However, personally, I don't see any reason for it. The official statement is "Since the Universal Editor follows a more streamlined, modern approach that does not support these le...

Hi everyone, I have a client requesting to migrate their existing, classic AEM components to Universal Editor (UE). They do not want EDS, just UE. Now I know it is not officially supported by Adobe, but given the universal nature of the UE, it should be technically possible. I was wondering if anyon...

The answer is: Experience Fragments (XF) cannot be assembled server-side in EDS like we are used to with classic AEM. Possible alternatives are: Expose XFs via API and load them client-side in EDSSwitch to EDS fragments, which are again client-side rendered Therefore, this might be challenging for c...

Hello, Universal Editor supports Experience Fragments (XF) [1], but does this work in combination with Edge Delivery Services (EDS)? There is an EDS block called Fragment [2], but the sample is built only for document-based editing, and I am not sure if it works with AEM. Has anyone tried it? Does i...

Hi @manavpadhariya, I don't think that's a valid use, so you should either use UE or DA for editing your content. Keep in mind, both content sources can be delivered with EDS. So you can have some sites stored in documents and edited with DA, and some sites stored in AEM, edited with UE.   Good luck...

Hi @Dyanamic, Universal Editor is a different story, AFAIK, there is a plugin available from Adobe to enable MSM-like features in Universal Editor. So you can break and revert inheritance on the component level, like in the old Page Editor. I am not sure if this plugin is GA already, so best to reac...