Thank you for sharing. Maybe you can move this to the blogs section as well: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/bg-p/adobe-experience-manager-blogs

Hi,    Did you try to add the "new" node as mentioned in the thread you shared? https://github.com/adobe/aem-core-wcm-components/issues/421#issuecomment-455230521 That seems to be the solution.    Hope this helps. 

Hi,    1. [Node.js] executes JavaScript code outside of a browser. npm stands for "node.js package manager." Straight from the npm website   2. YES 3. The ui.frontEnd module within the POM has a plugin that downloads a local version of Node/npm to build and compile the files from the module    Lastl...

Hi,    Follow the instructions from the archetype: ui.frontend/README.md Go to "ui.frontend" and run "npm run start"   Hope this helps

Hi,    AFAIK, the standard Core Components are designed for the traditional Page Editor, not the SPA Editor. If you're using a React-based setup, you should use the Core Components specifically built for SPA use. I'm not sure if a Carousel component is available for SPA, but you can check here for t...

Hi   The simple answer is that an AEM project consists of several modules, including both Frontend and Backend components. While you're likely already familiar with the Backend, which typically uses Maven and Java, the Frontend by default uses Node.js, npm, JavaScript, and potentially any modern JS ...

Hi @ButhpurKiran    No, there isn’t anything like that available. I believe the reason is that the architecture you're referring to is already tailored to a specific scenario, whereas the archetype is meant to be a flexible, open starting point.   The closest you might find is a demo project (like t...

Hi,   These are different products, each designed for a specific purpose. Asset Share Commons isn’t actually an official Adobe product — it’s open-source. You can learn more about the differences here: https://www.aemtutorial.info/2021/06/difference-between-brand-portal-asset.html https://experien...

Hi @Shankar_K    AEMaaCS blocks traffic for non-standards ports, if your API is listening in a non-standard port, you need to configure the Advanced Network Config, please check this: https://aemsimplifiedbynikhil.wordpress.com/2024/06/27/advanced-networking-in-aemaacs-http-https-connections-on-non-...

Hi @RebinR1    Product Functional Tests are managed by Adobe. If they’re failing, it’s best to raise a support ticket with Adobe. That said, these tests can sometimes fail due to odd or temporary conditions, but often pass when you rerun the pipeline. Have you noticed this happening consistently?   ...