you have to put all static resources (icons, images, etc.) in the
subfolder with name "resources", see
I also recommend to use the ACS Commons flush rules. However there is
subtl problem with cache invalidation levels if your the content
structure of your experience fragment does not exaclty match the
structure of your site. Assume you have a site structure of
/content/// with statfileslevel of 4 and use
/content/experience-fragments// structure for your XFs.
You will have a flush rule like
"/content/experience-fragments/([^/]+).*=/content/$1". that means you
invalidate your brand tree. The dispa...
I had the same issue with adapting sling XSSAPI. If you use the
(meanwhile deprecated) com.adobe.granite.xss.XSSAPI it can be adapted
without any problem. You can also adapt it right from sling request.
The exported files have currently a custom XML format. Is there any
reasons why they're not in xliff? Because xliff is at least the
well-known format the content translators already use in AEM
translator.Is xliff support for translation projects in the roadmap of
future AEM versions?