The jQuery transformation type allows you to use the jQuery transformation #{ColumnName} syntax to access properties of a document while still being able to use the {%%} syntax for Kentico specific macro expressions. This way you can create transformations that will work for both client side jQuery and server side Kentico.

The instances where you might use this are probably slim to none, but it is a nice feature to have if you like to use jQuery and AJAX to load markup into the DOM.

I believe the reason they added this type was to make it so you don't have to create/edit 2 transformations and to allow you to access the transformation through the API to output into your code for use with jQuery. It helps to make it backwards compatible with the current viewer controls that don't let you select 1 transformation for server-side and 1 for client-side code. You can essentially just say "Use this jQuery type template that will work the same with the MacroResolver as it will with jQuery's transformation parser".

Does that help answer your question?

Hello.

I am afraid we don’t have more information regarding this topic in our documentation, or some particular example. However, it says that you should use this transformation type when you want to resolve jQuery templates. So, it is just an option for you if you want go with these jQuery template. Otherwise, you can use any other transformation type which fits your needs, usually the default one. More info about jQuery templates can be found online, e.g. here, as this is jQuery related technique.

Best Regards,
Radek Macalik