Adobe Experience Manager Sites

A recruiter called me last month.She had an open AEM Product Manager role. Been open for 3 months. Plenty of applicants. But none of them understood the new AEM.Here's what changed —AEM isn't just a content management system anymore.Adobe just launched MCP Servers inside AEM — meaning developers can now use AI tools like Cursor, Claude Code, and Visual Studio to write, debug, and deploy AEM code without leaving their editor.They also launched LLM Apps — a capability that lets brands build experiences that live directly inside AI interfaces like ChatGPT and Gemini.Think about that.Your website content... delivered inside an AI conversation.AEM is quietly becoming the backbone of how brands show up in the AI era.But most hiring managers are still writing job descriptions for 2022.The AEM talent market hasn't caught up yet. The candidates who understand this new AEM? They're rare. And they know their worth.If you're hiring AEM talent right now — the bar has moved.Are your job descriptions

I'm developing an Adobe App Builder integration to sync product data present in Salsify to AEM Content Fragments via the OpenAPI in my RDE environment. IMS OAuth authentication is working correctly (I'm obtaining tokens with the correct scopes: aem.fragments.management,aem.folders), and I've added my OAuth Server-to-Server credential to the "AEM Sites Content Managers - Author" product profile in Admin Console.However, when my App Builder action calls the Content Fragments API (GET /adobe/sites/cf/fragments), I receive a 403 Forbidden error with: "IMS Client ID not allowlisted. Allowlist the Client ID using the Configuration Pipeline."How do I properly configure my RDE environment to allow this OAuth Client ID to create and manage Content Fragments?Specifically:(1) What is the correct method to allowlist the Client ID in an RDE  environment (2) Should I add the OAuth credential to any other product profile instead of "Sites Content Managers"?(3) Is there additional RDE-specific configu

404 error handler is implemented by overlaying the 404 from /libs/sling/servlet/errorhandler/404.jsp but changes 404.jsp to 404.html. And Java class to handle the request. on Dispatcher enabled below two flags<IfModule disp_apache2.c>        # Enabled to allow rewrites to take affect and not be ignored by the dispatcher module        DispatcherUseProcessedURL    On        # Default setting to allow all errors to come from the aem instance        DispatcherPassError        1  </IfModule>Java class have  -import com.adobe.cq.sightly.WCMUsePojo;public class PageNotFound extends WCMUsePojo {    @Override    public void activate() throws Exception {        getResponse().setStatus(404);        getResponse().setContentType("text/html");        getResponse().setHeader("Dispatcher", "no-cache");        getResponse().setHeader("Cache-Control", "no-store, no-cache, must-revalidate, max-age=0");        getResponse().setHeader("Pragma", "no-cache");    }}And html have  -<sly data-sly

In our Adobe Experience Manager internal portal(Azure OIDC auth 6.5 instance) the homepage invokes a few APIs that fetch data from a database and store user-specific responses in Redis.We normally conduct performance testing with 18,000 concurrent users (2 publishers with ~9,000 virtual users each) over a duration of 30 minutes. Prior to the upgrade, all API responses were consistently under 1 second.Recently, we upgraded to AEM 6.5 LTS (SP21) running on Java 21. After the upgrade, under the same load conditions, the average API response time has increased significantly to around 11 seconds.There are no functional issues observed, and all APIs are working as expected. However, this performance degradation is only noticeable during load testing.Has anyone encountered similar performance issues after upgrading to AEM 6.5 LTS SP21 or moving to Java 21? Any insights or areas to investigate would be helpful.

AEM as a Cloud Service is being used with ContextHub for personalization. After compilation, 32 JavaScript files(These files are already exists in code) are bundled into contexthub.kernel.js.A requirement exists to create a custom default segment that differs from AEM’s OOTB DEFAULT segment.The custom default segment was created using the following JavaScript:JavaScript(function () {    'use strict';    var MyDefaultSegment = function () {        return true;    };    /* register function */    ContextHub.SegmentEngine.ScriptManager.register(        'Region-Default',        MyDefaultSegment    );})();Show more linesScoring configuration:All region-specific segments (for example, Region-AA) are assigned a boost of 500Region-Default is assigned a boost of 2 (minimum boost)This works as expected when content is authored for all regions on the page.The issue occurs when a region-specific segment (for example, Region-AA) is resolved but no content is authored for that segment. In this scena

Hi everyone,After a successful Kick-off to AEM User Group Benelux chapter —We’re looking for speakers for our next session!Whether it’s a short demo, a case study, or lessons learned from your AEM projects. If you’re interested in sharing, we’d be happy to support you and feature you in one of our upcoming Quarterly user group events.It will be a wonderful opportunity to share your thoughts with fellow AEM practitioners, and inspire their thinking to explore what’s possible with AEM.Your session will also be recorded and hosted on a closed YouTube channel to benefit other AEM enthusiasts and practitioners.What topics would you find most valuable? Are there challenges, use cases, or ideas you’d like to explore in future sessions?Feel free to email me at: shruti.damle@deptagency.com or connect with me on LinkedIn to share your thoughts or ideas.Looking forward to shaping the next session together!Cheers,Shruti Damle, AEM User Group - Benelux Chapter Leader

Hi everyone,I’m working with AEM Cloud Manager log APIs and wanted to check if anyone has found a way to fetch logs incrementally (delta) instead of downloading logs based on a fixed number of days.Currently, the API supports downloading logs using a days parameter, but this results in retrieving the full log data each time. I’m looking for a more efficient approach where we can pull only the new log entries since the last request.Has anyone implemented a workaround for this or is there any supported way to achieve delta-based log retrieval?Appreciate any insights or suggestions.Thanks!

After upgrading to ACS Commons 6.15.4, ACS Commons pages are no longer editable via editor.html as they were in 4.x (for example, Dispatcher Flush and Adobe League pages now appear read‑only). Is this expected behavior? Do we have any supported workaround to retain the old page‑based editing model, or is using an older ACS Commons version the only option?https://xxxxxxxxx.dev.xxxxxxx.adobecqms.net/editor.html/etc/acs-commons/dispatcher-flush/test-lts.html  

Can you give the solution to customize and create the RTE plugin for external link builder experience in RTE for AEM to add the anchor tag and have data-link-attrs for modal popup inside the a tag

Using the OOTB sitemap for the generation. Added the generated screenshot below. loc url should be starts with /us/en and .html should be removed. I followed the this url as well not working as expected. Sitemaps | Adobe Experience ManagerAny comments or suggestion will be helpful Thanks in advance.  

I have a requirement for Hide show 2 different feilds on the basis of 2 radio buttons in same tab in page properties and i also want to persist either data on the basis of authoring. How can i acheive this in aem. Below one is not working. (function (document, $, Coral) {    "use strict";    $(document).on("foundation-contentloaded", function () {        var radioGroup = $(".cq-dialog-radio-showhide");        var target = radioGroup.attr("data-cq-dialog-radio-showhide-target");        if (!target) return;        function toggle() {            var value = $("input[type=radio]:checked").val();            console.log("Selected value:", value);            $(target).each(function () {                var $target = $(this);                var showValue = $target.attr("data-showhidetargetvalue");                if (value === showValue) {                    $target.removeClass("hide").show();                } else {                    $target.addClass("hide").hide();                    // 🔥 al

Hi all,I'm working on an AEMaaCS workflow and would like to implement a custom Participant Step dialog with dynamic data coming from a previous Process Step.Here is my use case: An editor starts a workflow on a Content Fragment Editor receives a notification and completes the first task A custom Process Step collects all referenced nodes under the Content Fragment and stores them into workflow metadata like below: item.getWorkflow().getWorkflowData().getMetaDataMap() .put("discoveredNodePaths", collectedPaths.toArray(new String[0]));   In the next Participant Step: Editor opens the task from Inbox A dialog should display all discovered node paths as a checkbox group Editor selects some nodes and clicks "Ok" The selected nodes should be saved back into workflow metadata Next Reviewer step: Reviewer opens task and sees selected nodes Can approve or reject If approved, a Process Step publishes all selected nodes My questions is about step4: How can I customize the Participan

Hi Team,Question 1I am using cloud SDK and experiencing jcr:title and jcr:description is not getting sync when I use OOTB rollout from master to live copies.anywhere I can look into custom configuration and add these properties.How to add them if they are not added ? Question 2I have checked libs/msm/wcm/rolloutconfigs and could not find anything related to these properties such as exclude node. I checked in apps/msm and could not find a custom configurations either so that meant we are using OOTB configuration only ? in that case do we need to raise a adobe ticket for this ?

 Hi Team,We are facing an issue on a multi‑locale AEM site, where some users from the EU region are seeing broken/distorted pages.SymptomsBrowser console shows errors indicating that CSS files are not loading properly In the Network tab, we see a 301 redirect happening for a ClientLib CSS URLExampleOriginal ClientLib URL:https://domain.com/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssRedirected URL:https://domain.com/de/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.cssSince /de/etc.clientlibs/... does not exist in AEM, the redirected request ends in a 404, which results in the page breaking.ObservationsThe same behavior is reproducible using a curl request (301 redirect observed) There are no references to /de/etc.clientlibs/...: Not in AEM configuration Not in Dispatcher Not in rewrite rules The only place where this URL appears is in CDN logs, where it shows cache=pass We are not caching an

Description:We are working on customizing the AEM Translation Project workflow to simplify the project creation experience.Requirement:The goal is to reduce unnecessary fields and configurations in the Translation Project creation dialog and project overview.Specifically:Remove unused properties from the Project Initialization Dialog Set a default translation language Restrict project templates and pods to only translation-related ones Ensure removed properties are not visible later in the Project Summary/Overview Only the Translation Project template should be visible during project creation. After the project is created, in the Add → Translation Job option, only the source languages "en" and "de" should be available for selection. What We Tried:Attempted overlay of:/libs/cq/core/content/projects/templates → /apps/cq/core/content/projects/templates Manual overlay via CRXDE Lite (facing errors) Verified permissions and access Compared configurations across environmentsFinally:     1. I

Hi All,We have migrated from a 3rd party DAM provider to AEM AssetsWe are now replacing the 3rd party dependency and package by changing the sling:resourceType FROM custom path "/apps/3rdparty-connector/core/ui/components/content/custom-pathfield" TO sling:resourceType="cq/gui/components/authoring/dialog/fileupload".Our Sites Program and Assets Program are different and hence need to be connected via Remote DAM Asset Selector. To do so, we have added the configuration "com.adobe.cq.ui.wcm.commons.internal.services.NextGenDynamicMediaConfigImpl.cfg.json" to connect to remote DAM Instance.We are able to connect to DAM Instance and using remote option for image selection able to select the image and display it in our pages. (Delivery URL Sample - https://delivery-p0000001-e0000002.adobeaemcloud.com/adobe/assets/urn:aaid:aem:00099990-0001-46f7-9a19-f0csd229b0d2d/as/test.png) However, we are missing few things.1. Ability to filter assets other than images (Videos are not supported)2. Metada

The LTS Analyzer identified a handful of references to obsolete components in our custom code, which we remediated and were removed from the report on a subsequent run.What remains are many paths to out-of-the-box components that we have never used or referenced.  In our dev system, I used the Content Transformer to remove ALL paths (/content, /etc, /libs, /var) on both author AND PUBLISH instances, PRIOR to upgrade (6.5 SP21).After upgrade, everything is working fine.  Zero issues.  But now I am seeing conflicting information that the tool should not be used that way, specifically:Only /content and /etc paths should be removed by the Content Transformer. The Analyzer should only be run on author instances.  On publish instances you should remove the obsolete paths manually or some other method (not sure what that would be). And just to confirm, the Content Transformer must be run on a 6.5 classic instance, prior to upgrade.  It errors out on a upgraded LTS instance.  The error logs in

I’ve been exploring how to better structure travel-related content so it aligns more closely with real user intent rather than just static destination pages.For example, users today are searching for very specific queries—like airline policies, visa requirements, multi-city routes, or realistic itineraries—rather than just “things to do” in a city.Some approaches I’ve been testing:Building query-first content instead of generic guides Structuring destination data (attractions, logistics, timelines) in a reusable format Keeping content modular so updates (like travel rules) don’t break the systemRecently, while working on a travel platform called Trekhops, I’ve been trying to implement this kind of structure more actively—focusing on how users actually search rather than how content is traditionally organized. It’s been interesting to see where this works well and where it gets challenging.For those using Adobe Experience Cloud or similar ecosystems:How are you handling dynamic, intent-