AEM - Adobe Experience Manager
Master Adobe Experience Manager with practical guides on implementation patterns, real-world problem solving, and best practices.
Real-World Scenarios: The Carousel With No Slides to Navigate
A hero carousel that renders navigation arrows and indicators but no slides — tracing it back to an inherited Core Component dialog tab that got hidden without anything replacing what it authored, and the contract test that would have caught it pre-launch.
Real-World Scenarios: Flipping a Feature Toggle's Default Changed More Pages Than Expected
A one-line change to an inherited page property's default value quietly changed behavior on hundreds of pages that had never explicitly set it — how it was traced, and the audit query that should have run before the change shipped.
Real-World Scenarios: A Shared Icon Picker's New Required Field Blocked Saves on Three Unrelated Components
A compliance-driven field added to one shared dialog subtree quietly became a required field on three components that reused it via node-level sling:resourceSuperType — tracing the save-blocking bug back to an invisible dialog dependency, and the CI check that finds every consumer before a change ships.
Real-World Scenarios: An SEO Audit Found Every noindex Page Still Listed in the Sitemap
A quarterly SEO audit found that a noindex exclusion feature in a custom sitemap generator had never worked in production — traced to an untyped multi-value property read and a Java array's default toString(), plus two related fixes for vanity-path alternates and template-mismatched hreflang links.
Real-World Scenarios: A Rebrand Silently Broke Every Experience Fragment Created Before It
A site-wide theme consolidation changed a handful of page properties and left dozens of previously-created Experience Fragments visually mismatched — with no errors anywhere, because a ResourceChangeListener had copied those properties at creation time instead of inheriting them live.