For your first question, you dont need any separate space other than the size of the tool. oak-run-1.2.11.jar has around 48MB and if you have so much to store that file would be sufficient.For the second question, compaction runs on repository folder and the size difference would definitely reduce m...

As part of this migration, is UI  (templates and components) is changing ?If yes, then you can look at number of pages/content you have.If its pretty much less, then I would prefer migrating it manually considering the effort in automating it. If you have larger volume of content, then you can write...

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...

Sightly templating script is designed not to have such logics other than just rendering piece of it. As @edubey mentioned, you can use JS Use API or do all that operations in your Sightly model or sling model class itself and send the actual value which needs to be displayed.

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