@aanchal-sikka I know about the usual ways to achieve this and the best practices. I was mostly interested in technical workarounds when, due to different reasons, like the the constraints I mentioned above, one is not able to do it properly, but rather needs a quick rather 'brutal" way to deploy bu...

Hi @aanchal-sikka  But assuming I am not able to do this, as I stated at point 3, what other way is to deploy it in publish instances ? I would add even a stronger constraint, that being that publish instances have the /system/console forbidden at infra level and we don't have yet a infra team that ...

 Assuming I have the following context:1. Project is inherited, the solution is pretty rigid, and we lack project know-how2. Stakeholders pressure is pretty high, so a time-delivery balance has to be found, which usually means no-too-much-time-for-best-practices 2. Infrastructure architecture is com...

Hi @Shaheena_Sheikh  Can you share an example from your local ? In your screenshot I see they all show up both page name and title.There is no specific config as far as I know. One value is the JCR node name, the other is the jcr:title property.

Hi @laniweisbart I see a couple of things:- one is an issue with maybe too many assets that need to be traversed by your logic- the other looks like an HTL error within a component of yours. Maybe the second derives from the first, assuming that the traversal error does not allow your logic executio...

1. Please check the logs for any hints.2. See if your manager has all necessary permissions3. If you use Dynamic Media, check the configuration and connection4. Try to refresh, maybe only the label "processing" does not get refreshed (but I doubt it) These are just few straight forward thing to look...

AEM has some good documentation on how and why to use Tags: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/siteandpage/tagsBut here we are talking about taxonomy, which is only a concept helping you to decide how to organize your tags, the idea being to late...

Unfortunately I haven't experienced this nor do I find much documentation on this on the internet.Dis you find this already ? https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/maven-build-failure-repositoryexception-inaccessible-value-500/m-p/260828 Could it give you any hint...

If you have different teams managing each site code base and/or you want to manage separately the release strategy and/or you must run independent gitflows, then I think having unique maven modules would be fit. And everything that is common from site-a would be moved to a commons module and extende...

Hi @LearningisKey I found only this old thread on something similar, nothing else out there. Please check if it helps. It talks about permissions on AEM server's folder location on the OS:https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-3-package-installation-issue/td-...