Thanks JaideepBrar​ for the suggestion.  Given a vanity url example of '/annual-reports', how would you configure apache so that it knows whether it should redirect to page request in the CMS under /content/wherever or to an asset in the CMS under content/dam/wherever?  And in the case of assets wh...

Thank you for the suggestion ka786​.  I wondered about sling internal mappings but I'm not sure I would describe that as "authoring-friendly"(?)

Hi is there an equivalent vanity urls feature for DAM assets?Are there other authoring-friendly ways to achieve something similar (with minimal developer involvement (e.g. sling internal mappings))? For example we'd like to have a vanity URL for a terms-and-conditions document hosted in the DAM.  Th...

Thanks for the suggestion hamidk11679710​​.  We are aware of the advice to move clientlibs out of etc/designs (and note: our issue does not involve http 404 errors as in Clientlibs not loading the fonts when placed in apps).  Our issue is not seen when requesting pages directly from a publisher inst...

When we upload a new custom clientlib - to etc/designs - and then do a tree activation, the next time we request a webpage that includes those font files, then the font files are created in the dispatcher with file size 0.  The resulting impact is that when requesting a web page in the browser, font...

smacdonald2008​ this requirement, to have a “request publication“ workflow for individual DAM assets (as there is for pages), feels like it should be a standard OOTB feature. is there a formal way to request this as an enhancement to forthcoming AEM releases?thanks

I was looking at how to add a favicon for a site and saw this thread.  Sounds like the approach is different now to the one linked above: with AEM core components, using the page component and editable templates, we can now specify a client library (provided we have set "allowProxy=true") as the loc...

Thanks again John for your suggestions. My forum question here is not a programming one. It's about using the Target GUI. When we try and edit one of our existing website pages (served by Aem) the Target GUI - that allows you to highlight parts of a page and change text and images - fails to correct...

John thank you very much for taking the time to reply. We have written our components via a javascript framework: Vue.js. Our components make extensive use of custom html elements. So i suppose the root of my question is: do custom html elements pose a problem for Adobe target, in terms of locating ...

We have components in Experience Manager written via a javascript framework.  As a result there are custom html elements in our markup.  This is presumably quite a common scenario.  Target seems to struggle to work with this markup - in terms of amending text and images.What should Target be able to...