Hi @nsvsrk ,Here's a concise overview of the flow of control in AEM, from frontend (HTL) to backendLet’s break down the Flow of Control in your scenario, where a page is built using Template T and Components C1, C2, and C3, and the frontend is in HTL (Sightly) while backend logic resides in Sling Mo...

Hi @ButhpurKiran , Thank you for the comprehensive explanation and the thoughtful comparison of the two approaches.In our case, Node.js is not functioning as a full backend service—it acts solely as a lightweight wrapper layer to render and serve the React application. It doesn't handle business log...

Hi @PRATHYUSHA_VP , Thank you for the detailed suggestion.You're absolutely right—if the page data is available via AEM GraphQL, generating the sitemap dynamically makes sense. However, in our current setup, Node.js is used only as a lightweight wrapper layer and not as a full backend service.Given ...

Hi Adobe Community,We are currently transitioning from traditional AEM Sites to a headless architecture where AEM serves as the CMS, and the frontend is built using React with a Node.js backend.In this setup, we're using Content Fragments delivered via AEM’s Graph QL APIs and no longer rely on tradi...

 A REST (Representational State Transfer) API is an architectural style that allows communication between client and server over HTTP.