Hi @HarshaSi, Unfortunately, here's the hard truth about the AEM jar file: AEM Jar Access: Not Publicly Available Adobe does not provide AEM jar files (Quickstart JAR) for public download, even for learning or evaluation purposes. Access is strictly limited to: Customers with an active Adobe Experi...

Hi @Joelcio, You need to customize the dialog of the component by overlaying it. 1. Overlay the Dialog Copy the Experience Fragment V2 component from /apps/core to your project’s /apps/your-project/components/experiencefragment path: /apps/core/components/experiencefragment/v2/experienc...

@aa_w  You're right - TeaserImpl is marked as internal and not designed for direct extension. Since it's not part of the public API and getTargetPage() is protected, it’s not accessible from a custom implementation via inheritance. However, you can still customize the Teaser v2 component to support ...

Hi @AryaBa1, I would suggest to use AEM’s MSM (Multi-Site Manager) to inherit structure but allow local overrides. Combine this with editable templates for flexible but controlled site management. Use a separate /conf folder per site or brandExample: /conf/site-us /conf/site-uk /conf/site-fr E...

@olsalas711  1. Multiple GitHub integrations: repo vs branch When we say “multiple GitHub integrations”, we are not recommending multiple repos per environment unless necessary. Instead: Correct approach: Use one GitHub repository, with separate branches (e.g., main, dev, staging), and create separa...

Hi @olsalas711, 1. Can you explicitly select the branch when creating an Edge Delivery site in Cloud Manager? Currently, no - Adobe's EDS Cloud Manager UI does not provide an option to choose a different branch during site creation. By default, it uses the main branch of the linked repository. 2. Wh...

Hi @aa_w, I think, Teaser v2 or most of the components introduced stricter internal URL resolution via PageManager.getPage(), which prevents external URLs from being recognized correctly in getTargetPage(). To restore the v1-style behavior (i.e., allow any valid URL, including external ones), you’ll...

Hi @AryaBa1, Managing environment-specific configurations should be done using Context-Aware Configuration (CAC) in combination with runmode-specific OSGi configs. Here's a breakdown of the recommended approach: 1. Use Context-Aware Configuration (CAC) CAC allows you to store config values in the c...

Hi @OmarKh3, To implement cascading dropdowns in Touch UI dialogs, you can use the Granite UI datasource approach with JavaScript listeners (using coral-change event) and a servlet to populate the dependent dropdown dynamically. 1. Define your dialog with dynamic state dropdown Create your cq:dialog...

Hi @sgreddy, That the know issue and I have experienced it before:Touch UI metadata schemas (via the Metadata Schema Editor) do not directly reflect in Classic UI (Asset Editor). They use different mechanisms for rendering asset metadata forms: Understanding the discrepancy Touch UI uses /conf/glob...