Refer this https://github.com/adobe/aem-guides-wknd-spa for github with react project and code.   And this for creating a new react component: https://experienceleague.adobe.com/docs/experience-manager-65/developing/spas/spa-implementing-react-component.html?lang=en 

Hi @vasimakram , If you are able to see your index in CRX/DE.  Then I would suggest to check these 2 points: If customizing an out-of-the-box index, for example damAssetLucene-6, please copy the latest out-of-the-box index definition from a Cloud Service environment using the CRX DE Package Manager ...

I am not sure which workbook the training videos were referring to. But, you can always go over to the partner portal if you're a partner with Adobe or you can also go to the learn section of this website. They should be enough to cover aem assets. https://experienceleague.adobe.com/?lang=en&tag=AEM...

Hi @aem-enthu27 ,   There is not a 1:1 match in local SDK for AEMaaCs and for Dev/STG/PROD, as they have many microservices running there. But you can enable it, follow this: https://wttech.blog/blog/2020/handling-aem-as-a-cloud-service-renditions-in-local-development/   

Can you briefly explain your use case/requirement @vasimakram ? It'll make it easier to get to a solution.

Hi @PoovithaSelvaraj ,   If you're referring to the content translation, you can either create a custom configuration.  But, the best way to take care of that is GlobalLink as it is already present with the Experience Cloud.   Reference:  https://experienceleague.adobe.com/docs/experience-manager-64...

You can download the environment variables as a JSON file from the API provided by adobe: https://cloudmanager.adobe.io/api/program/{programId}/environment/{environmentId}/variables After that, you can easily store them in Docker.   Reference: https://developer.adobe.com/experience-cloud/cloud-manag...

fulltext will just look for certain fields like node name or jcr:title. If you need to expand or restrict the nodes it searched for, you can use fulltext.relpath   fulltext.relPath is the relative path to search in (eg. property or subnode) eg. fulltext.relPath=jcr:content or fulltext.relPath=jcr:co...

This is a rule within AEM where a query will stop after traversing a certain amount of nodes. There are 3 ways in which you can overcome this:   1. Add more identifiers to your query which will narrow it down and search for less nodes.  Example: sling:resourceType, fulltext etc. Why this works is be...

Hi @con84758 ,   The best approach to re-use a component (OOTB or custom) is to proxy that component. That means, adding the property  sling:resourceSuperType = <path_to_component> to the component. Now, if you want to extend a html for the same, you cannot extend that in 2 ways: 1. Copy the html fi...