Thanks @muskaanchandwani ,Yes, it is deprecated, but what is the best way to enable or use Core Components in an AEM React SPA project? Many brands are still actively using AEM with React SPA.

Thank you so much @AmitVishwakarma 

so currently for me cache invalidation is not working and before moving for the auto replication. Frontend team has updated routing from index.tsx. Which resolved the cacheing issue. I'm just understanding the the process as this is my first time to work on AEM+REACT. // @TS-nocheck import "react-a...

Thanks for the detailed explanation @AmitVishwakarma!, So essentially, only the en.model.json (our SPA root) should be rendered and not individual page JSONs like home.model.json or about.model.json, correct?

Hi @ShivamKumar ,Thanks for your prompt response. I've already tried the solutions you shared, but none of them worked — except for the first one. I'm specifically trying to understand why the model isn't updating automatically if we're using a React SPA. In your first suggestion, you mentioned auto...

If you're using AEM 6.5, could you please confirm which WKND codebase you're working with? If it's based on the following repository https://github.com/adobe/aem-guides-wknd/blob/main/archetype.properties then please note that it's intended for AEM as a Cloud Service, as specified in the archetype.p...

@SachithaKo2 ,   If you want to allow both Brand A and Brand B templates when creating pages under either brand, you need to add the templates from both brands to the 'Allowed Templates' field on the root page of each brand. same for Brand B

@RekhaRa4 , In your pom.xml, the property aem.sdk.api is set to: 2023.7.12874.2023072678702512-230702 This is an AEM as a Cloud Service SDK version, not for AEM 6.5!That means your project is compiling against AEMaaCS APIs, which are slightly different from AEM 6.5 on-premise APIs. That's why the in...

@JulkarNa1 ,I already tried with responsive grid approach but it is creating unnecessary layout container around components.      

@sravs , I’ve applied all the suggested fixes and explored every possible solution. Below is the implementation of my exporter model. package com.mysite.core.models; import com.adobe.cq.export.json.ComponentExporter; import com.adobe.cq.export.json.ContainerExporter; import com.adobe.cq.export.json...