I've achieved the same thing using a different approach.Instead of uploading each rendition as a separate DAM asset, we instructed our authors to upload renditions directly to the primary asset (full resolution)[img]https://docs.adobe.com/content/docs/en/cq/5-6-1/dam/how_to_edit_metadata/_jcr_conten...

Check the code for the Activate Tree feature: https://docs.adobe.com/docs/en/aem/6-1/author/page-authoring/publishing-pages.html#Activating a complete section (tree) of your websiteI believe that the page is no long included by default in AEM 6 unless you start the instance with the "samplecontent" ...

Is there any documentation for the CQ Javascript API? We are doing a lot of custom component development, but we don't know which helper functions are available, unless we randomly find them in someone else's code snippet.Some examples:CQ.WCM.getEditables() CQ.I18n.setLocale('de-DE')CQ.I18n.get("May...

Does anyone know how to configure a CQ component so that each property can be cancelled individually inside of a Live Copy? I am trying to have it set up the same way as the Page Properties, so that canceling one property does not break inheritance for all of them.Page Properties:[img]http://i.imgur...

Doesn't that create a huge overhead by having all images + renditions stored once for each region? Out of curiosity, how does the tool in 6.1 handle the end result? Does it duplicate the DAM asset or overwrite the original dc:title, dc:description?

Thanks Scott.That looks interesting, but I'm not sure that I fully understand the result of translating an assetNode. Does the node in the DAM get translated? If that's the case, does the origin page now point to a translated Asset?For example, if I have an image set with dc:title and dc:description...