This is a 2 part question regarding EDS handling of javascript and CSS. Part 1: AEM 6.5 has a feature that minifies javascript and CSS. Does EDS have a similar ability or is this an optimization step that must happen inside the GIT repo? Part 2: Adobe AEM Commons has a "Versioned Clientlibs" feature...

The Sites tool at /sites.html has a left rail that can display "Lent Content" references for a selected page. What is considered Lent Content and is there some kind of osgi configuration it requires? I couldn't find any documentation on it and perhaps someone might know its purpose. References Panel

I'm working on an AEM 6.5.9 servlet that needs to use a PKCS8 format private key to sign a JWT for a third-party application. This is not related to setting up SSL or other Adobe services. Can the private key file be stored in the crx-quickstart folder or is there a different preferred approach? And...

Assign your CSS clientlib to the "cq.authoring.editor.core" category documented at https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/reference-materials/jsdoc/ui-touch/editor-core/index.html

This technique also works in 6.3.

One approach is to create a new CSS clientlib and assign it to the "cq.authoring.editor.hook" clientlib like so: <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="cq:ClientLibraryFolder" categorie...

Our short term solution to this problem was to take the AEM 6.3 version of /libs/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js and install it as an overlay at /apps/cq/gui/components/authoring/editors/clientlibs/core/js/model/Inspectable.js in 6.4. Its hasPlaceholder me...

In my view, sites are easier to maintain if the dispatcher is set to "allow" content by default so authors can deploy new language folders under /content without requiring any adjustments to dispatcher rules. Ideally the dispatcher rules are never a bottleneck for authors who are pushing out new con...

A basic approach that I've seen used successfully is to put a site-specific property at the root page of the site, like at /content/site1/en_us, and then adjust the component to inherit that property using InheritanceValueMap like this:InheritanceValueMap ivmap = new ComponentInheritanceValueMap(res...

This appears to be a dropzone bug in touch ui. My component has cq:dropTargets in its editConfig and I can fix the problem by removing cq:dropTargets but I need cq:dropTargets because it is needed for in-place editing of the component's background image. I may need to create an Adobe support ticket.