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,   What @arunpatidar shared is basically all you need to do/check at some point, for a quick analysis and evaluation i would suggest starting with the Best Practice Analyzer: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journe...   Hope this helps

Hi,   Unfortunately, this can sometimes occur. You can reach out to Adobe through their support ticket system in such scenarios.

HI @selenere1    I think you are mixing terms and concepts. Please find the answers below: Is it possible to logically and securely segregate development, pre-production, and production environments within Adobe Experience Manager (AEM)?Yes, this segregation is in place by default. Each environment...

Hi,   The warning typically appears when an outdated pattern is used to create user mappings (the username was not enclosed in brackets). Your current configuration looks correct. For more details, please refer to the documentation here:https://experienceleague.adobe.com/en/docs/experience-manager-c...

Creating a new plugin is more complex than simply extending an existing one. I’d recommend adding your custom styles to the style plugin instead. However, if you’re set on developing a new plugin from scratch, you can refer to the following resource for guidance:   https://www.bounteous.com/insights...

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,   You can enable the "style" plugin to achieve exactly what you're looking for. It allows you to define and apply multiple custom styles, each of which wraps the element in a <span> with the specified class.   For more details, please refer to the following resource: https://experienceleague.ado...

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