/etc.clientlibs/... is the correct "new path prefix". This denotes that the CSS/JS/Static resources are in a client library that has allowProxy set to true. These "proxied" clientlibs exist under either /apps or /libs (as they are code, and code should be in /apps or /libs). If you see these request...

Gotcha! If the datasource.name is variable based on a dialog then i'd continue to do what youre doing! looks good!

Just a quick note, @reference should be @Reference (capital R). Then, OSGi configs in the JCR must be in folder named "config" (or "config.<runmode>") that is no more than 4 levels from the root; So it should be at: /apps/source360/config/com.day.commons.datasource.jdbcpool.JdbcPoolService-SIADB Las...

EDIT: I just realized you werent asking about AEM Sites .. im in the Assets community afterall!!  There isn't a natural hook to at GTM to the AEM Assets *authoring* experience. I think you would have to either: 1) Try to find all an OOTB clientlib category that is loaded "everywhere" in the authorin...

There some JCR-level constraints outlined here: https://jackrabbit.apache.org/oak/docs/constraints.html That said, I try to stick with: lowercase, alphanumeric using hypens for separators, because:- names are unambiguous- names are easily human-readable- names work well in URLs and do not require es...

I believe you need to do this using the browser's "default" request for /favicon.ico -- you can obviously conditionally re-route this request in Apache Webserver (or even in a AEM servlet if you wanted to write one) - I think there should be context that the request is "for" a binary request by look...

You can customize (including removing tabs) from metadata schemas using Tools > Assets > Metadata SchemasCheck this video out for some details:https://experienceleague.adobe.com/docs/experience-manager-learn/assets/configuring/metadata-schemas.html?lang=en#configuring

This would be a great post to copy over to the Idea's section of Communities, so this feedback can be provided to AEM Product Management team.

Point to the ACS Commons component using the sling:resourceSuperType property on your cq:Component.

If have a (reasonably ) finite number of inputs producing a (reasonably) finite number of permutations of JSON - you could also look at using HTTP Cache [1] to cache the entire JSON output in AEM memory and serve it from there. [1] https://adobe-consulting-services.github.io/acs-aem-commons/features...