Adobe Experience Manager

It would be extremely helpful if the Adobe Cloud Manager UI displayed clear information on which user initiated a pipeline execution as well as which user approved or rejected the pipeline in the approval step.Today, identifying who triggered or approved a pipeline often requires navigating through logs or API calls, which is not intuitive. Having this information surfaced directly in the Cloud Manager interface would provide:Better traceability – Quickly identify the person responsible for starting a deployment or making an approval decision. Improved auditability – Essential for teams that must comply with governance, security, or compliance standards. Faster troubleshooting – When a deployment causes issues, teams can easily see who initiated or approved the pipeline and follow up with the appropriate individual. Enhanced collaboration – Team members and stakeholders can more effectively coordinate by knowing who has taken action at each stage.Displaying the triggering user and the

How Adobe Dynamic Media Templates close the gap — delivering personalized content at scale from a single URL. For the designers, marketers, and developers who have to make personalization actually happen. The personalization imperative Personalization isn't a nice-to-have anymore - it's the default customers expect. As per this McKinsey study, 71% of consumers expect companies to deliver personalized interactions, and 76% get frustrated when this doesn't happen. And it pays: companies that grow faster drive 40% more of their revenue from personalization than their slower-growing peers.So the mandate is clear. The problem is delivering on it. The content scale crisis Personalized marketing demands creative at a scale no design team can hand-produce. Every product needs creative for every channel, in every language, for every audience, refreshed every campaign - and those factors don't add up, they multiply. Run the numbers for a single year: 8 products × 15 channels × 35 languages × 10

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for June 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:De

Choosing the wrong authoring model can impact content velocity, governance, and scalability. Here's a practical comparison to help AEM teams make the right decision.This guide breaks down the key differences in authoring experience, content governance, flexibility, scalability, and implementation considerations to help teams choose the right approach for their AEM EDS projects.Whether you're building marketing sites, enterprise platforms, or content-heavy experiences, understanding when to use each model can save significant time and effort. Read More:- https://www.aemcq5tutorials.com/tutorials/document-based-authoring-vs-universal-editor-in-aem-eds/ 

 Hey all,Most AEM teams trust the Dispatcher's deny-all approach, but are your allow rules as restrictive as you think?In this article, I explore how broad extension-based allow rules can expose internal endpoints in AEMaaCS and share practical hardening recommendations for a stronger security posture.🔗 Hardening AEMaaCS— Part 3: Why Default Dispatcher Rules May Expose Internal EndpointsCurious to see any similar experiences anyone had!

This is a request to have the Emergency pipeline execution mode, currently available for AEM on-pem (Code Deployment | Adobe Experience Manager), added to AEM as a Cloud Service. 

I like the Question asked by @Viktor Lazar  here The 2026 question is "what is the content supply chain that produces the experiences, and where does the component library fit inside it?" If New Age AI Architecture looks like this (taken reference from https://www.trainyfi.ai/post/aem-is-no-longer-the-brain-ai-is) AI Agent Layer   ↓Calls into:- AEM (content)- AEP (data)- Target/Journeys (activation)   ↓Continuous optimization loopI have a few key questions from an AEM developer’s perspective:How should AEM components be designed within this new AI-driven ecosystem? What should AEM developers specifically focus on when building solutions in this model? Where is the “working model” in practice, given that it no longer resides solely within AEM? How will this shift toward AI-driven orchestration shape the future role of AEM and its component architecture?Given that the “working model” is now distributed across AI agents, AEP, AEM, and activation layers, how do we practically design and al

Please ping me at John@syncpointdigital.com if you are interested in learning more. 

Hello awesome community guys, I found one missing tool in AEM MCP arsenal. Ended writing a custom mcp server that runs on AIO AppBuilder as runtime action.Explained here https://medium.com/@bsaravanaprakash/one-missing-tool-in-aem-mcp-registry-and-how-to-build-it-on-aio-902cc13b1afaWith this learnt experience, I quickly identified couple more tools usecases on my custom mcp server.Optimized product image search - tool will first hit PIM to resolve to more accurate tags and then hits DAM querying customized tags. Returns accurate product images Taxonomy Resolver - our DAM is massive (3.4M) and taxonomy follows rules. freetext image search mostly timesout due to volume. So custom tool, that runs taxonomy rules, narrows dam folder path and then run Adobe MCP asset search using querybuilder.  Is there any more usecases you are able to find? Tool example, that is difficult with Adobe MCP registry, and qualifies for its own custom server?  Please do share, ready to flex my muscles.

Hello everyone,I wanted to get your feedback and suggestions on steps to follow while starting on implementing analytics for AEM Adaptive forms in a headless setup.Since a JSON flows back from AEM, should AEM responsibilities just be restricted to maintaining standard field definitions and the rest of the tagging happens on the front end renderer (React) ?Any pointers would be greatly appreciated.

Hello team! We are looking for people that have experience with AEM and lives in México, we at Capgemini have some opportunities for you :) 

👉 Calling all AEM practitioners in the San Francisco Bay Area and beyond ‼️👋We're thrilled to announce the launch of the AEM User Group - Bay Area chapter! Hosted by seasoned AEM experts KrishnaKalyan Gorthi and Mrinal Kumar, this is a community dedicated to passionate AEM users who come together to share best practices, collectively problem solve, and network.This chapter will host in-person and virtual meetings, so there is no shortage of ways to connect with your peers. 🙌Sign up here: https://aem-augs.adobe.com/aemug-bay-area/

Planning your next AEM EDS implementation? AEM Sites or Edge Delivery Services (EDS)?Explore the complete differences in architecture, content authoring, deployment pipelines, performance, developer experience, and migration considerations to choose the right solution for your digital experience platform.  Click here to Read More

Hi all,I need to conditionally exclude some fields from the auto-generated DOR through code. Nothing I’ve tried to program is working.Please, how can I emulate in code what the “Exclude From Document Of Record” checkbox does? It works correctly when I use the UI checkbox, but if I try to do it via code in the Value Commit event, it doesn’t work. I’ve tried things like:field.dorExclude = true; field.excludeFromDoR = true; field.dorExclude = true…but none of it works. Thanks in advance for your help!Any guidance would be greatly appreciated.

Technology and Digital Transformation

As a Principal Product Manager on Adobe’s Digital Employee Experience team, I focus on understanding and meeting enterprise content needs across Adobe—using Adobe products to do it. My team runs and operates our internal Content Hub, and we truly drink our own champagne by acting as Customer Zero. In a previous post, I shared how we create Branded Experiences with Experience Manager Content Hub and AEM Sites. In this post, I share how we utilized an early access, UI Extensibility feature in Content Hub to enable assets that have restricted licenses, to be requested--thus expanding potential opportunities for asset reuse, which reduces costs and makes better use of our original content creation.  Key Concepts Digital Rights Management: see this DRM post for a great overview of what’s new in DRM UI Extensibility: Content Hub supports UI extensibility (currently in Limited Availability), which enables the addition of custom UI components to the Content Hub UI for specific workflows and bu

Curious how enterprise AEM Cloud teams are evolving Content Fragment modeling strategies as AI-driven personalization and multi-channel delivery become more common.Historically, many content models were designed primarily around page rendering and headless delivery needs. But with increasing AI-assisted content generation and dynamic experience orchestration, the modeling requirements seem to be changing rapidly.Interested in perspectives around:reusable fragment design metadata strategy AI-friendly taxonomy structures personalization scalability GraphQL performance considerations and governance for large content ecosystemsWould love to hear how teams are preparing their content architecture for more AI-driven experience delivery models.

AEM Sites Developer Professional free online training with exam preparation. Have a question about the AEM Foundations course, AEM Sites Developer Professional course, or the Certified Professional exam prep guide listed on the certification information page? Reply to this thread and a learning support specialist will respond to you.  We follow the Adobe Experience League Community Forum Guidelines in this discussion thread. If the response resolves your question, consider giving a Like to the learning specialist who replied. We appreciate the kudos! Questions outside the scope of the online courses and exam preparation guide will be directed to the main community forum page. 

The second part of a series is now published on Perficient’s website: Implementing Headless Page-based Authoring in Adobe’s Universal Editor. (The first article can be found at here.)Link to the article → https://blogs.perficient.com/implementing-headless-page-based-authoring-in-adobes-universal-editor-part-2/  

Most DAM governance models we inherit are designed for a problem that no longer exists. The closed authoring loop is gone. Content Hub, MCP endpoints, and Brand Experience Agents have opened it, and the governance has not kept up. What is breaking in productionStale rights metadata reaching external partners through Content Hub. AI generated variants with no lineage back to the source. Tags that look right but were produced by an LLM without controlled vocabulary alignment. Distribution portals shipping content past its expiry because nothing on the way out re-reads the policy. What is working for us so farGovernance lives in metadata, not in folder paths. Folder structure is a navigation aid. Rights, lifecycle state, AI provenance, market scope, and approval state are schema fields, queryable and enforceable in workflow.Rights management is a first class object, not a tag. Model release, talent expiry, and market exclusion need their own model with start and end dates, and a workflow

 Headless using AEM Sites, not only Content Fragmentsby @daniel-strmecki Introduction Headless delivery in AEM is often associated with flexibility, performance, and modern frontend architectures. For developers, this usually sounds like a clear step forward. However, in many enterprise projects, headless has also introduced a major tradeoff: marketers and content authors lose access to many of the AEM Sites features and the familiar WYSIWYG editing experience they rely on every day.This is why "headless AEM" is still too often reduced to "Content Fragments exposed through GraphQL APIs". Content Fragments are powerful and absolutely have their place, but they are not the only way to build headless experiences with AEM. At least not anymore.With AEM as a Cloud Service, AEM Sites, and the Universal Editor, we can now take a more balanced approach: keep enterprise-grade content management and visual authoring in AEM Sites, while delivering experiences through a modern headless frontend ar

We are excited to announce our Adobe Experience Manager Champion of the Month for May, ​@VidyR​!  Vidy was a clear choice for this recognition, as she truly embodies the spirit of the Adobe Champion Program. Not only does she actively raise her hand to support key initiatives like speaking on our upcoming Champion Application webinar, writing articles on Perspectives, and sharing feedback with our AEM Assets Product teams, but she regularly attends AEM Champion social events and fosters relationships outside of programming. She is a rising star in our community, and the program wouldn’t be the same without her bright personality. Thank you, Vidy, for your leadership and commitment to the Champion Program!  

As MCP adoption continues to grow, organisations using AEM can unlock even greater value from AI-powered development tools by providing richer project context and domain-specific knowledge to their coding assistants. Have you integrated GitHub Copilot and MCP into your AEM development workflow? Share your experience and favorite use cases in the comments below Set Up JetBrains with GitHub Copilot and AEM MCP

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for May 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:AEM

  ResourceFilterStream: An Optimized Alternative to Query Builder in AEM       by @mayursatav    Introduction Efficiently querying content is a fundamental challenge in Adobe Experience Manager (AEM). While the Query Builder is a powerful and widely used tool, it can become a performance bottleneck when dealing with large result sets, potentially leading to high memory consumption and slow response times. The ResourceFilterStream offers a highly optimized, server-side alternative for filtering resources, providing a memory-efficient and often faster solution for specific use cases. Understanding when and how to leverage ResourceFilterStream can significantly improve the performance and stability of your AEM application. Key points For developers building scalable AEM solutions, optimizing content queries is crucial. ResourceFilterStream provides a powerful tool for filtering large resource trees without the memory over