Looking for some ideas here on the best way to handle the following
scenario specifically as it relates to AEM Sites and Translation. 1. We
have pages that have been translated from a Global English Master to
various languages through a Translation Provider (SDL and others). 2.
When the translations come back, inevitably our in-country marketers
want some tweaks here and there which are then made manually to the
resulting AEM pages. At this point we are good and everything works
perfectly. 3. We...
So we have a number of experience fragments our authors have created and
we want to export them as plain HTML. According to the documentation,
you simply use the .plain. selector in the URL and poof it should work.
This doesn't seem to work so questions: 1. Are you supposed to be
hitting the XF directly? If so, how do you construct a URL to hit the XF
directly?2. Are you supposed to add the XF to a page and then use the
selector? We tried this, but .plain. just returns the same page.3. Are
I fully understand why Adobe would not want to make it easy to delete
Projects given there are downstream integrations that could be affected,
but the inability to delete and manage anything in the interface is
entirely frustrating. As far as we can tell, even accidentally clicking
"Create New Project" gives you a permanent project even if you have done
nothing within it in terms of hooking to any other tools. Long term
management is very frustrating, sunsetted integrations you can never
This is odd because we clearly see a jQuery library with the following
v1.12.4-aem * http://jquery.com/ * * Includes Sizzle.js *
Our site currently implements jQuery at the global level, but it also
appears that Target also injects an un-minfied version of jQuery as
well. Is it necessary to do this or is there some way to disable this.
It does affect page load because it render blocks and while it doesn't
affect code it seems silly to have duplicate references. If not, can we
at least minify it through some config? Thanks very much.