Awesome! That worked!! Thanks kautuksahni

I have not been involved in such an implementation. However, my thoughts are that you store a value in the profile to check whether it is the user's first login/first visit to a specific page. If yes, then trigger the overlays. You will have to customize the existing core UI, and that would be a bit risky. Probably have a specific clientlib and call the clientlib on the check, or else the js files will be loaded on each visit. Checkout [1] for a framework that supports what I think you need. 1. ...

The below link explains a good example on how to write js for events, such as a validator. It explains the concept of the extraClientLibhttps://docs.adobe.com/ddc/en/gems/customizing-dialog-fields-in-touch-ui.html

Have you tried using design components? Site level values can be stored there, and editors / authors can update those values via the Design context. You can specify a template's designPath as the Global path (eg. home page template), and any design level updates to that design path can be used across any template by accessing the value via code.

We setup CI with Bamboo. You have to install the Maven executable, and then use Maven for the deploy etc...

In my experience, design dialogs and touch UI don't go very well.The only way to get a design dialog to open in Touch UI is if you embed it into the page component via data-sly-resource with the path as a parameter. Dragging and dropping into the par will not work in Touch UI, but will work in Classic UI. Try and see if this works for you. This works for me in 6.2, so not sure if there is an issue, it may be a 6.1 specific issue.

Stumbled upon this while troubleshooting similar issue of deleting the /var/clientlibs. Recreating the folder did not work. After adding permissions to everyone jcr:all, it worked. Hope this will help someone else.