Thanks @arunpatidar, will share it today on LinkedIn and would appreciate your feedback

Hi @BohdanYurevych,I did solve that in my Next.js demo, you can watch it here: https://www.youtube.com/watch?v=wJx4kLeGVucSo the solution was to add a custom button in /apps/wcm/core/content/sites:<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http:...

Hi @durga_kavali,on the initial project setup, I always delete modules I am not using to keep the project as simple as possible. You can always add it later. For example, if your project is headless then you probably don't need the ui.frontend module.However, sticking to the default AEM project stru...

Hi @jooca,this depends on your requirements, usually starting with a simple AEM search is OK for the MVP, but things get more complicated later in case you want to add facets or index data from 3rd party systems.In case you already know you will have complex search requirements, implementing it with...

Hi @kartheekd203042,here is what I did and its working fine:

Hi @AlbinIs1,not really, for me, it didn't work when I tested it some time ago. If someone from Adobe can confirm that would be great.

Hi @kartheekd203042,I did it like this: when you override the default schema and add a new tab, AEM copies all the tabs in /conf/global/settings/dam/adminui-extension/metadataschema. I just deleted all the default tabs in CRX and left only my custom tab, and it's working fine. Good luck,Daniel 

Hi @konstantyn_diachenko,how are you running it on Publisher? Can you explain?Catching replication events on Publisher in AEMaaCS is more tricky compared to On-Prem, as there are multiple publisher PODs and you usually want to catch the event and process it only once. Therefore, you can use the Disc...

Hi @konstantyn_diachenko,AFAIK the example you shared will catch the replication event on Author, not on Publisher. I can confirm this approach is working fine on my project. Also, you should not re-implement this with com.day.cq.replication.Preprocessor as that API is not supported on AEMaaCS. Good...

Hi @Tethich,good point, I am not sure, only if they use AEM's CDN for both domains/hosts. I guess the author can clarify.