Yes, you can do this with the ui.frontend, which comes apart of the AEM Archtype, https://github.com/adobe/aem-project-archetype. Within the ui.frontend, you can update the NPM modules, and instead of using SCSS, you can use LESS. So instead of using sass-loader, you can use less-loader, https://web...

Also, yes if your status of servlet is not "Active", then this means that you may have some dependencies to resolve. Can you verify if all bundles are "Active"? 

Here's what you need to do, exactly: Login to AEMVisit http://localhost:4502/crx/de/index.jsp#/libs/cq/xssprotection/config.xmlOverlay the XSS protection configuration by copying /libs/cq/xssprotection into /apps/cq/xssprotection (and all it’s children)Delete the /apps/cq/xssprotection/rep:policyFro...

To reuse scss variables and javascript utils in your ui.frontend (if you have multiple repositories), I would create my own private npm modules. For CSS, reference to sass-loader | webpack, and for sharing JS utils, you can create a private npm modules to export JS for consumption of your ui.fronten...

What's the exact usecase? Maybe instead of using the JCR_SQL2, you can get the resource of that particular path, and then get childrens of that resource?

Can you access /etc/designs from your local machine, author, publisher? Are you referring to dispatcher? Maybe the dispatcher have a limited restriction for accessing the path /etc/designs... or maybe the everyone user does not have permission to this resource path?

You need to make sure you have the correct AEM version & service pack installed. The data-sly-set is available for Version 1.4 sightly compiler installed. An implementation of version 1.4 of the language specification is available in AEM 6.3 SP3+, AEM 6.4 SP1+, and AEM 6.5+. If you have access to sy...

I would use AEM Style System for this approach. Using the style system will require CSS changes only. Say for example, if your container has an active style system of "Verticle Scroll", then this CSS class name will be appended at the root level of the component... looking at the root element of tha...

Here's a query you can use. Find me all cq:PageContent nodes, where properties exists: jcr:created, jcr:createdBy, jcr:primaryTypeand it must be nodes under the paths of /libs/fd/af/components/aemform or /content SELECT page.* FROM [cq:PageContent] AS page WHERE page.[jcr:created] IS NOT NULL A...

Here's the query for finding all dam:Asset objects which does not have any tags configured. In layman's terms, find me all assets under the /content/dam/sourcedcode folder, where cq:tags does not exists. type=dam:Asset path=/content/dam/sourcedcode property=jcr:content/metadata/cq:tags property.oper...