That's great, I'll check it out -- thanks!

Thanks, Ankhur, that makes sense -- thanks for addressing the difference!

Thanks, I'll read through the upgrade portal. I hope the AEM 6.3 docs get updated soon; the current docs are very confusing. Thanks for running down this info for me!

Sorry, that didn't help at all. While the page you linked to says it's about using Dynamic Media with Experience manager, the recorded session in fact talks about Lazybones and Editable Templates. On top of that, I'm not at all happy about watching videos to get product information; I'd much rather ...

I'm trying to understand image handling capabilities in AEM and the documentation leaves me more confused than when I started.in the AEM 6.3 docs under Working with Assets there are sections for Adding Scene7 Features and Working with Dynamic Media. The docs indicate that if I enable Scene7 I can't ...

I posted this on StackOverflow at aem - How to emit the server path to the current file using Sightly? - Stack Overflow and got a satisfactory answer:Create a JavaScript file that asks Sling for the path to the current file:component-path.js:use( function() {    return { "path" : sling.getScript().g...

Sorry, I should have been more clear. I want a way to automatically inject the path to the current file. I don't want to hard-code it; I want a single snippet of code I can drop into each file that echoes the current path. That way, if I move the file, the comment automatically updates. I did this j...

I have some components that I've broken into multiple smaller files. The main file includes them using data-sly-include attributes.I'd like to generate HTML comments containing the current filename in both the main file and the included files, so that when I view the rendered output I can easily tel...

That worked perfectly -- thanks!

I have a problem similar to this one: Sightly in <script> tag not evaluating? In that thread, the problem was that Sightly expressions inside a script element were not being rendered, and the solution was to add @ context = 'scriptString' to the expression.My situation is a slightly different:...