One quick thing you can do to eliminate whether it is an AEM issue or a network issue, is to login to the AEM server's shell and execute a curl to consume the webservice and see whether you get a response back. If you do get a response, then the issue is with AEM. If you don't then, then it is most probably a Network issue.

Awesome! That worked!! Thanks kautuksahni

Is this for use of a design component?Usually, the design is in the form of the following /jcr:content///In some patterns of implementation, there is also a clientlibs folder in the design path.Usually, these are all versioned in the CVS (eg git or svn). If you keep a filter to include this path, it will be persisted in your local filesystem.Hope this helps.

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

can you please share the renderer config, which links the dispatcher with the publisher?

I don't think there would be any OOTB feature that allows this. The one closest is an OOTB option that allows users to add HTML via a component. You can, technically, have a template without any code, and then read the HTML that was added by an author and render the page. Checkout the RTE field.

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