@jayv25585659 You will need a deployment manager profile to be able to do that,

@kautuk_sahni Any idea why when we can expect this feature? The current permissions interface/mechanism is too complicated and  there isn't detailed enough documentation to support the current way of permissions management.

@nj2 You should probably start from here - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/migration-journey/getting-started#understanding-transition-to-aem-as-a-cloud-service   For your components , templates, pages you can use the BPA and modernization suites to...

@subrato_kha Looks like a bug, you might want to file a ticket with Adobe support and confirm with them.

@johns43992246 One way would be to create clientlibs at the component level so that you have component specific JS and CSS code instead of one big monolith file each for JS and CSS. You will have to decouple your CSS and JS code into component local and Global code. The piece of clientlib code that ...

@bethen5 You may want to refer to this discussion - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/always-start-aem-coral-ui-datepicker-with-today-s-date/td-p/404372  

@Srinivas_Opti  Sign in  with Adobe uses your Adobe account Org's IMS credentials that you dont have access to in your local instance. You can log into your local instance using a valid AEM user stored locally in your AEM environment's JCR.

@Vishal_Jain03  use @Mock instead of @reference  Make sure that you setup any objects / object attributes in the Setup method (this is the one with @BeforeEach annotation) For instance, if you need the ResourceResolver from the ResoruceResolverFactory mock object, the inside the setup method, you sh...

My 2 cents on this topic @kautuk_sahni , @cbunchjr From a performance perspective, this might be a no-go as sorting nodes adds extra overhead and if you have a very large tree, then it may even cause the whole process to fail.

@VeenaVikraman Yes, the major downside that i have seen with such architectures is that there is a very tight coupling wrt JS and CSS code. You are basically going to load the clientlibs as single monoliths most of the times instead of just loading the code that is actually needed on a specific page...