As Scott mentioned, same component can support both touch UI and classic UI without any problem. All the JS which needs to be executed by the classic UI should be referenced in the classic UI dialog and I am not sure why that JS would be included in JSP. Rather, keep it as a part of clientlibs and t...

Can you give more details on your usecase

What is the difference in rendering between these two UI ?Are the properties different in each of these dialogs or just the rendering style ?

I dont see any options for it. You may have to customize the service when the page is created to read that value and store it.

Goto /libs/foundation/components/page/cq:dialog/content/items/tabs/items/basic/items/column/items/title/items/hideinnavand add a property 'checked' and value 'true' of type 'String'. It will set the value checked by default.However, you will have to overlay this tab in your <project>/components/page...

Hit <host>:<port>/projects.htmlClick on Tools -> Operations -> Deployment -> Offloading

For your usecase, you will have to write a custom authentication handler and OOB is not available

From AEM 6.x, recommended approach to use SQL2 or JQOM for queries You can refer JQOM example here : http://adobeaemclub.com/jcr-java-query-object-model-jqom-adobe-aem-query/

Which AEM version are you using ??I am able to see these offloading jobs in AEM 6.1

Hi Rama,I think Google translations is a paid service. Look at the pricing model here [1]. If you have it, then you can use the APIs and create a translations workflow[1] https://cloud.google.com/translate/v2/pricing