The Sling Resource Merger and the related methods can only be used with Granite. This means that creating an overlay with a skeleton structure is only appropriate for the standard, touch-enabled UI.Overlays for other areas (including the classic UI) involve copying the appropriate node and entire su...

Refer https://adobe-consulting-services.github.io/acs-aem-commons/pages/maven.html   

Create a common clientlib which required across the webpages or page component based clientlib.And keep component specific clientlib separately .And if you want to reuse any existing clientlib then you can embed as well. refer https://github.com/AdobeDocs/experience-manager-cloud-service.en/blob/mai...

Use component level clientlibs 

Refer core component for navigation . https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/navigation.html?lang=en#example-localization 

Try with archetypeVersion=27

Use sling:resourceType as /libs/granite/ui/components/coral/foundation/form/pathfield

unpack the jar file in crx-quickstart folder .Under that /bin /start.bat

Are you referring to get content pages as AEM data ?Kindly elaborate the use case . 

Check start.bat file config values CQ_JVM_OPTS=-Xmx1024m -XX:MaxPermSize=256MRef: https://stackoverflow.com/questions/59866778/aem-author-instance-is-not-responding