Localization is one of the first areas where many Adobe Experience Manager (AEM) implementations start to feel unnecessarily complex. Most projects start with simple requirements, such as adding a second language or translating a few pages. However, over time, the business expands its websites to su...

In Adobe Experience Manager (AEM), reusability is key to creating scalable and efficient digital experiences. Many teams begin by focusing on components, but components alone can only go so far. They define layout and functionality, but often blend content with design. This makes it difficult to reu...

When we make a request to fetch an asset from AEM as a Cloud Service (AEMaaCS), our request doesn’t go straight to the AEM Publish instance. Instead, it’s handled by Adobe’s OOTB CDN, which sits in front of AEM Publisher and serves cacheable content directly from the edge. If the asset isn’t already...

Are you running your Cypress tests during the Maven build process? In AEMaaCS, the right place to run Cypress is the Custom UI Testing step, which executes your tests inside a Docker image that already has the browsers/display stack.   Good luck, Daniel

Request for Feature Enhancement (RFE) Summary:Content picker in the New CF Editor allows only browsing assets, not sites/pages.Use-case:Our CF models contain CTAs linking to pages.Current/Experienced Behavior:Editor needs to manually find and copy and paste the correct link to a page.Improved/Expect...

Hi @Ben_Hu, I've used JSON forms (https://jsonforms.io/docs/) to achieve a similar kind of hide/show functionality, but that was for the new Content Fragments Editor. Maybe you can check with Adobe Support if JSON forms are supported in the Universal Editor? It might be not be GA yet. Here is an exa...