After a lot of research, looks likeAdobe Experience Manager (AEM) 6.5's launch console is limited to adding pages. It doesn't currently support adding assets directly.Launches are designed to create copies of pages that can be edited and published at a later date, allowing for planned content update...

Thanks for the detailed steps @HrishikeshKa Re:  Steps 3, 4 .. I am not able to find DAM / AEM Sites Launches specific integrations/permissions. Sorry to stretch this..                 User "admin" has all the permissions.

Thanks @HrishikeshKa I am using AEM default "admin" login, assuming should have access to all paths?How can we verify this?Verify Configuration: Double-check your AEM configuration to ensure that the DAM is properly integrated with AEM Sites Launches. Make sure that the DAM is configured as a valid ...

Thanks @gkalyan How can i check the DAM content paths in the Launch?The other adobe community link shared was more about Content-fragment-model and CF's created using that model. We have several CF's under "content/dam/project/cf-hub" built usingthe Content fragment model at "/conf/project/settings/...

We have site pages under project "/content/project/en/us/page-1" , and some of these page have components that fetch content from content fragments under "/content/dam/project/cfs/CF-1" While creating an AEM > Sites > Launches (<server>/libs/launches/content/launches.html ) , we are able to add Page...

While running some Translation projects, AEM logs reported "consider creating an index or changing the query". We added an Index (oak:index) as below:   But adding this Index is causing the Translation jobs to fail ("failed to start translation"). Logs showing as:  java.lang.IllegalArgumentExcepti...

jQuery 1.12.4 has security vulnerabilities (listed below). Are there any plans to upgrade jQuery on AEM 6.5 to the latest jQuery 3.6.x ?  Although, we do see a custom jQuery v1.12.4-aem , did Adobe fix some of the vulnerabilities?   As of now, even on AEM 6.5.14, comes with jQuery 1.12.4   The docs...

We can use as below to refer to the template of the component we are referring to. For example:cta.html <template data-sly-template.renderCta="${ @ style, ... }"> <div class="cmp-cta ${model.ctaAt}" ... Another-Component.html <section data-sly-use.model="com.eb.web.models.component.TextColu...

Thanks for the suggestions. Re: this https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/touch-ui-dialog-include-part-of-another-dialog/m-p/265153/highlight/true#M58331 when we use "include" , we cannot control the name of the component. So this was causing both primary and sec...

Good observation @Lavanya_Pejjayi but that did not resolve the issue. I was trying a few options and may have added the code. I updated the component html in original question.