Hi,   Could you let me know which AEM version you're using? From your description, it sounds like it might be a race condition — possibly a required dependency for the bundle you mentioned isn't starting consistently, which could be causing the issue you're seeing. I’d recommend starting a fresh loc...

I completely agree with @daniel-strmecki — if an upgrade is already on your roadmap, moving to the Cloud is the best path forward. That’s where Adobe is investing most of its effort, and the platform has matured significantly. Even for sensitive data, AEMaaCS is now well equipped (for example, it al...

Hi,   The command you're using is meant to create a new archetype—a project skeleton—for your own AEM project. In contrast, the WKND project is a fully developed reference implementation. The -DarchetypeVersion=39 flag specifies which version of the archetype you want to use. Archetypes evolve over ...

Hi @lumen5, if you're retrieving assets (data) from a different server—which I understand is non-AEM—then it's a completely different scenario. You'll need to expose your data via an API and use it within a custom widget. The specifics of the widget and its implementation will depend on where you in...

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,    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 @rawvarun    The key is defining the Environment Variable and marking the scope for "all" services. Then using the syntax like this: ${{MY_VAR}}   Hope this helps

Hi,   Is this on AEM as a Cloud Service? If so, why do you think the deployment is not going through? It’s possible that the reindexing process is stuck. You can check this using the Repository Browser—if you're on AEM Cloud, you should be able to verify whether the index is present there.   https:/...