Hi @kautuk_sahni ,Any update on this request?

Hi All,Can you please let me know how asset-manifest.json file is created while building wknd-spa-react projectI created the react spa-editor based project using steps mentioned here: https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/rea...

Hi Team,Is it possible to create Page/Template base on SPA Editor but the Header and Footer experience fragment should be rendered from server side, only the body/main section should be dynamically rendered using react.In our project we already have Header and Footer experience fragments which are n...

Hi Team,In our project we are using core wcm component version "2.21.0" but the aem spa-project-core (latest) is build on core wcm component version "2.15.0".If we plan to use aem-spa and spa-project-core in our project, will there be any effect due to version mismatch.

Hi Team,When I try to store product data feed to be used in Recommendations. The Feed section shows that data has been injected successfully: But when I try to search the products in Catalog, no products are visible. I tried multiple time but its not working. Can you please help.

Team any update or guidance ?

Hi @Shashi_Mulugu ,We have tested the feature in lower environments (Non-production pipelines), want to be sure we can use in Production environment (licensing needs etc.) 

Hi @EstebanBustamante ,In initial phase while exploring the front end pipeline feature one of the Adobe SME had mentioned about this.We did not do anything specific for Stage and deployment was successful. But want to ensure no issues with no Production Deployment.

Hi Team,We are already using Full Stack and Web Tier Deployment pipelines for Deploying code to Production in our AEM Cloud environment.Is separate licensing needed for using the AEM Front-end pipeline usage for Quick Site Theme deployment?

These links does not contain anything specific to Production Deployment. We have deployed/promoted our code till Stage. We wanted to ensure nothing is missed while doing deployment to Production