Adobe Experience Manager

Thank you to Karthik Muralidharan, Director, Strategy and Product Marketing, for the insightful presentation and demo on Adobe Brand Visibility! So many exciting things coming to the Generative Engine Optimization space!If you missed out, or want to replay the session, check out the links below:Slides Webinar Recording Check out the product yourself: play.bv.nowFeel free to use this space to keep the conversation going! Add your thoughts, follow-up questions or takeaways here and maybe let us know what feature you’re most excited about.If you missed it, check out the session we did in July with Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com. They shared their experiences of marketing in the world of AI. Also, save the date for September 22, for our next AI Search and Discovery Forum session – registration link coming soon!

You’re invited to The Skill Exchange 2026, a free virtual event running August 5-6 and August 11-13. Looking to sharpen your Adobe skills, discover new ways to work smarter with AI, and learn directly from Adobe experts and customers? This is the event for you! Skill Exchange 2026 registration is officially open! 🚀  Join us for:✨ Expert-led sessions across 7 Adobe solutions  🤖 AI-powered tips and innovations  💡 Real customer stories  🎬 Live demos and practical takeaways you can apply right away  🤝 Opportunities to connect with fellow Experience Makers AEM Sessions are on Wednesday, August 12th!Whether you're just getting started or looking to level up your expertise, there's something for everyone. 🎟️ Save your spot today: [Register Now]  

If your team is planning (or mid-way through) a migration from on-prem AEM or AMS to AEM as a Cloud Service, here's a rundown of the things that tend to blindside people beyond what's in Adobe's official migration docs.1. The "no full read/write access to the repo" shift is bigger than it soundsOn-prem, you got used to poking around CRXDE Lite, hotfixing content in prod, or running ad-hoc Groovy scripts against the JCR. Cloud Service locks that down hard no CRXDE Lite in prod, no direct repo shell access. Everything has to go through code, content packages, or the Cloud Manager pipeline. Teams that relied on "just SSH in and fix it" workflows need to rebuild that muscle memory around proper CI/CD and content sync tooling months before cutover, not during it.2. Cloud Manager's code quality gates will fail builds you didn't know were brokenCloud Manager runs static analysis (Sonar-based rules) on every build, and it's stricter than most teams expect. Common failures:Deprecated APIs (Reso

We're excited to partner with the Adobe AEM Customer Success team for a 4-part event series to help teams turn AEM Assets from a repository into a true part of the marketing operating model.Across these sessions, you'll build a working understanding of Adobe Experience Manager Assets - including how it supports content reuse, governance, collaboration, and omnichannel activation. Whether you're a marketer or work alongside one, you'll come away knowing not just what AEM Assets does, but how it helps your team find approved content faster, improve consistency, reduce duplication, and support business goals across every channelEach session will offer a mix of live presentation, demo, Q&A, and more: Sessions include:  August 19 - From Content Chaos to Content Reuse: How Marketing Teams Move Faster with AEM Assets September 2 - Find It. Trust It. Reuse It. The Power of Metadata, Taxonomy, and Governance ( ​@DanaPoliti ) September 16 - The Right Access for the Right Teams: Designing

🗣 Looking to continue the conversation after Experience Makers The Skill Exchange? The conversation isn't over.At Skill Exchange on August 12, AEM experts ​@ghowell15 and ​@pstolmar will take the stage — Gary with Scaling Content Creation with Product Launch Accelerator and Generative AI and Peter with Scalable Content Workflows for Authoring and Asset Governance. Afterwards, they'll host an open office hour built for one purpose: to keep that dialogue going with you.This is your chance to bring the questions you don't get to ask live, the use case you're still working through, or the challenge you hit the moment you tried applying what you learned. Come with your real-world scenarios — Gary and Peter will be here to work through them live.What you'll walk away withDirect answers from two AEM experts on scaling content creation with generative AI and building governed, scalable authoring workflows — grounded in what they're seeing in real implementations, not just theory Practical nex

🗣 Looking to continue the conversation after Experience Makers The Skill Exchange? The conversation isn't over.At The Skill Exchange on August 12, AEM Champions ​@BrettBirschbach and ​@venkatkrishnat will take the stage — Brett with Leveraging AI in AEM Cloud Service Development and Venkat with Content Authoring Evolution and Best Practices. Afterwards, they'll host an open office hour built for one purpose: to keep that dialogue going with you.This isn't a repeat of their sessions. It's your chance to bring the questions you don't get to ask live, the use case you're still working through, or the challenge you hit the moment you tried applying what you learned. Come with your real-world scenarios — Brett and Venkat will be here to work through them live.What you'll walk away withDirect answers from two AEM Champions on applying AI to AEM Cloud Service development and modernizing content authoring — grounded in what they're seeing in real implementations, not just theory Practical nex

Big news for the AEM community! 🎉 Adobe User Groups now have a unified home — and that means it's never been easier to find your people. Whether you're just getting started with AEM or you've been in the ecosystem for years, there's a local or virtual chapter where you can connect, learn, and grow alongside fellow users. What's new: ✅ One destination for all Adobe User Groups across Adobe Experience Manager, Adobe Experience Platform, Adobe Analytics, Adobe Commerce, Adobe Marketo Engage, and Adobe Workfront ✅ Increased event options around a multitude of topics and global locations ✅  More community-building opportunities within the Adobe CX Enterprise ecosystem  How to get started: Learn more about the new experience from our Community Pulse blog:  Find an Adobe User Group chapter near you 👉 https://usergroups.adobe.com/?cgen=1K8FD178&mv=other 

Been thinking about this a lot lately, and curious how other AEM teams are approaching it.For years, we've poured effort into hardening the perimeter around our AEM environments — VDIs, VPNs, SSO, locked-down repos, strict PR gates. Classic castle-and-moat thinking: keep the outside out.But here's what's nagging at me: with AI coding agents now part of the daily workflow, files like CLAUDE.md, AGENTS.md, and .cursorrules have quietly become some of the most information-dense documents in the repo. Dispatcher configs, content fragment models, component architecture, business logic — plain-English descriptions of exactly how the system works.And that's the actual problem: these files usually don't get the same treatment as code. They're committed casually, reviewed loosely (if at all), and often live at the repo root where any contributor — human or AI agent — can read them. Unlike obfuscated code or config buried three folders deep, this is a plain-English map of your system: auth flows

⭐⭐ Congratulations to ​@ghowell15, AEM Champion of the Month! ⭐⭐Gary is one of those Champions who doesn’t just support his greater AEM community, but shows up and shows out for his fellow AEM Champions. Whether it’s stepping up to lead a session at The Skill Exchange, partnering with other Champions and Adobe Product team members on Perspectives articles, or actively participating at a Champion social event, Gary is a true pillar within the Adobe Champion community, and we wouldn’t be as strong without his leadership, dedication, and positive attitude.Want to see Gary in action? Check out his Skill Exchange session, “Scaling Content Creation with Product Launch Accelerator and Generative AI" on Wednesday, August 12 at 10:30am PT: https://reg.adobe.com/flow/adobe/skillx26/landingpage?source=COMMUNITY&sdid=Y2KRGJ1X

🙌 Congratulations to ​@gkalyan, AEM Champion of the Month - June 2026! 👏 🏅 Kalyan has gone above-and-beyond in the last year as an AEM Champion, stepping into multiple leadership roles in the AEM User Group Program, internal Adobe product feedback sessions, and Community advisory. He regularly raises his hand to help mentor new and existing customers and serve as an advocate of the Adobe CX Enterprise ecosystem, including as a speaker at internal and external Adobe events like Adobe Summit. Please join us in congratulating Kalyan for this impressive achievement!

In AEM as a Cloud Service (AEMaaCS), the out-of-the-box (OOTB) CIF component Commerce Retriever APIs currently return Optional.empty() for both a successful GraphQL query that yields zero products and an execution failure (such as timeouts, HTTP 429s, or transient connectivity issues).Because both scenarios produce the exact same return value, custom implementations have no supported way to differentiate between them. This prevents us from delivering a tailored user experience, such as showing a "No products found" message versus a "Service temporarily unavailable" retry prompt.Proposed Implementation Approaches (Flexible):We leave the exact contract to Adobe Engineering's discretion, but viable options include:- Exposing a separate error object or status indicator.- Throwing a specific checked or unchecked exception on execution failure rather than swallowing it into an empty Optional.- Providing a metadata wrapper alongside the result.

What a fabulous discussion yesterday! Many thanks to Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com for sharing their experiences and insights on Generative Engine Optimization (GEO), as well as to our moderator, Karthik Muralidharan, for keeping the conversation flowing and engaging!If you missed it or what to revisit any part of the session, you can access everything below:Slide Deck PDF Webinar Recording Also, don’t miss out on our follow-up session on August 20. AI Search and Discovery Forum: Inside the Future of Brand Visibility. We’ll review the roadmap, recently released capabilities, customer success stories, and give an exclusive look at Adobe Brand Visibility. Register now! We’re looking forward to continuing these discussions and learning more from you. What are you seeing in the world of GEO? 👀

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 July 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:An

Test

Problem: the OOTB Content Fragment component makes every field of a referenced fragment editable in the Universal Editor. There's no supported way to expose some fields (title, body) while protecting others (slug, featured image, metadata owned by other teams). This is the default behaviour, not an edge case.I went down a deep rabbit hole and tried several approaches: The Field Contract Pattern worked: A proxy component whose editables point at the component's own node (so the rail resolves a model I control, not the CF schema), reading the fragment live for display and writing approved fields back via a ResourceChangeListener. Hidden fields simply aren't editables anywhere — enforcement by construction.Full writeup with code: Selective Content Fragment Editing in AEM Universal Editor: Building a Field-Level Editing ContractOpen question for the community and Adobe: is there a supported way to scope the CF schema returned to /details per editing context, or a cancellable pre-persist ex

Sharing your experience on Gartner Peer Insights helps peers make more informed decisions.Take 10 minutes to complete an Adobe Experience Manager Assets review on Gartner Peer Insights.👉  Submit your review here: https://gtnr.io/KPTRX1WC1  👈Important details to keep in mind:Reviews are anonymous. Only your role, industry, and organization size are displayed. Updated reviews are welcome. If you submitted a review in the past and have new insights to share, login, update your review, and submit. Gartner will assess and may publish quality updates. Personal emails aren’t accepted by Gartner. Log in using your business email or LinkedIn. Be thorough in your answers.

Many thanks to Aman Kumar Gupta (Senior Product Manager) and Siddharth Sahni (Senior Engineering Manager) for sharing their expertise on Content Hub! Thank you to the team for helping in the Q&A as well!If you weren’t able to attend live - or want to revisit any part of the session - you can access everything below. Session MaterialsSlide Deck PDF Webinar Recording Stay tuned for the consolidated Q&A from the session! We’ll posted it in this thread.Additional ResourcesContent Hub blogs: Unlocking Content Hub Extensibility Custom Workflows in Content Hub  Session SummaryThis session covered three pillars for AEM Assets Content Hub: Making content easy to find, Real to use for your business workflows, and Safe to govern. Key capabilities demoed included AI (semantic) search, custom sorting, on-the-fly generation of channel-specific dynamic renditions (e.g., Instagram/LinkedIn crops) from Search bar of Content Hub, auto-updating Smart Collections for managing multiple brands, an

Working with AEM Content Fragments in Adobe Journey Optimizer?Then join us for the next Experience League Live on July 16 at 8:30 AM PT as we explore the latest enhancements that make it easier for content authors and journey practitioners to collaborate, manage content at scale, and reduce handoff friction.In this session, we'll cover how to:✅ Fetch Content Fragments from multiple AEM configurations and switch repositories across journeys and campaigns✅ Manage fragment lifecycle from a new dedicated listing page in AJO✅ Keep content fragment context throughout the message for easier content reuse✅ Take advantage of locale and variation support✅ Access AEM Content Fragments directly in AJO with Managed Services. Whether you're an AEM author managing content libraries or an AJO practitioner building personalized customer journeys, you'll leave with practical insights into the newest capabilities and how AEM and AJO work together in a production content workflow.My guests are : ​@tkhwai 

The Article talks about how to integrate your Dynamic Media Renditions (AEM Dynamic Media Scene7 or Dynamic Media with Open API) via Content Advisor

Hi everyone,When teams plan custom transportation software, one useful approach is to define the measurement model before development starts. This is especially important for transportation, logistics, delivery, fleet, and dispatch workflows because the value of the software is usually tied to operational improvement, not just the number of features built.A practical way to measure Transportation Software ROI is to start with a baseline. Before replacing spreadsheets, manual dispatching, paper forms, or disconnected systems, document the current numbers. Useful baseline metrics can include cost per shipment, delivery delays, manual admin hours, invoice error rate, dispatch response time, fuel usage, empty miles, driver utilization, and customer support volume.After that, map each software feature to one measurable outcome. For example:A dispatch dashboard should reduce manual coordination time. Route optimization should improve delivery performance or reduce fuel usage. Digital proof o

Tired of maintaining versioned custom indexes in AEM as a Cloud Service?In this blog, I explore Simplified Index Management using Diff Index, a powerful feature that allows developers to maintain only index differences instead of full index definitions.✅ Migrate existing custom indexes✅ Create brand-new custom indexes using only diff.json✅ Validate and verify migrated indexes✅ Understand limitations and best practices A must-read for AEM developers looking to reduce index maintenance overhead and simplify upgrades.  Want to Read more :- https://www.aemcq5tutorials.com/tutorials/simplified-index-management-aem-cloud-service-diff-index/ 

Là nguồn tham khảo thời tiết dành cho cộng đồng Việt Nam, ThoiTietHomNay.org cung cấp các bản tin dự báo chi tiết, dữ liệu môi trường và những thông tin hữu ích liên quan đến khí hậu. Website hướng đến việc hỗ trợ người dùng đưa ra quyết định phù hợp trước những thay đổi của thời tiết. 

Many thanks to Senior Product Manager Mayank Gaur and Computer Scientist Priyank Modi for showcasing the power and possibilities of AEM Dynamic Media! If you weren’t able to attend live – or want to revisit any part of the session – we’ve compiled a summary, session materials and additional resources below!  Session SummaryThe session focused on how AEM Dynamic Media helps organizations move from managing assets to activating personalized, governed digital experiences at scale. Using a coffee product launch example, the presenters demonstrated how Dynamic Media enables automated image and video optimization, AI-assisted asset activation through the Content Optimization Agent, secure and governed delivery controls, and scalable personalization through Dynamic Media Templates. The event also covered reporting capabilities, upcoming roadmap enhancements, and customer Q&A. Session MaterialsSlide Deck PDF Webinar Recording Consolidated Q&A Additional ResourcesEvaluate Dynamic Media

Are you integrating AI into your AEM or Edge Delivery Services environment (or planning to)? Wondering how to do it without introducing security risks or governance gaps into your production architecture? This webinar took place on June 24, 2026. AEM Champion Krishna Kalyan Gorthi (​@gkalyan) will cut through the noise to share practical design patterns, real-world implementation guidance, and proven strategies for adopting AI responsibly in AEM environments. You'll get concrete, actionable takeaways you can bring directly back to your team. What You'll Learn:Where and how AI fits into AEM and EDS architectures for maximum impact How to proactively address risks like prompt injection, data leakage, and untrusted outputs Real-world implementation patterns across application code, OSGi configuration, and dispatcher for secure AI adoptionThe slides from this session have been attached to this post. This article will be updated as soon as the recording has been uploaded to Experience Leagu