Hi @rohitya2 Please align your environment with the Adobe recommendation for the latest archetype.Archetype Historical Supported AEM Versions: https://github.com/adobe/aem-project-archetype/blob/develop/VERSIONS.md
Tagging to the CF by authoring once. Adding the tags to the page from the tags associated with the CF is programmatically automated. Because OOTB there is no way to achieve it. So you need to implement some custom logics.
Hi @Prashanth_02a There are some advantages and disadvantages in both cases:Separate Client Libraries:Pros:Granular Control: With separate client libraries for individual components, you have more control over which resources are loaded on specific pages. This allows you to optimize the performance ...
Hi @dineshkumar_aem The issue you described with the Anchor Link Container and its dependent Title and Value components can be effectively addressed with a combination of backend Java (Model) and frontend JavaScript (Client-Side).To tackle the problem of the Title component being hidden on the first...
Hi @miniMeatball It is a designed behavior in Adobe Experience Manager (AEM) when authors create an Experience Fragment (XF) template containing both disabled and active components. When linking the XF template to another page under the sites, the disabled component will not be rendered on the page ...
Hi @gdWebct While avoiding the difficulty of duplicate and redundant author tagging, it is possible to expose content fragment tags into tag fields at the page properties level. The Adobe Experience Manager (AEM) ecosystem's strategic modifications and seamless integration can be used to achieve thi...