that because, this workflow is activated only for 'publish' instance

Hi Arnab,2 different things here..Sightly : Is the templating engine and it just controls the view script. So even without changing it from jsp to sightly it works as is and going forward any new components can happen in sightly. However, it is good to migrate slowly to sightly to be on safe if the ...

If your current application is already built in AEM, nothing wrong in upgrading the version !

Hi Debal,As Kunal mentioned, it advised to have it run on a daily basis by configuring such that it doesnt effect much ! 

You can refer [1].[1] http://adobeaemclub.com/aem-eclipse-plugin-setup-tutorial/

 I havent tried richtext in multifield but check this example if it helps [1][1] http://blogs.adobe.com/contentmanagement/2013/08/22/customized-multifield-richtext-editor/

Havent tried personally, but it looks like not support OOB. refer [1] and see if it gives a clue for you to get a workaround[1] http://stackoverflow.com/questions/30972256/aem-xtype-tags-within-multifield

Anything that will be set in the design mode, will be restricted to a template ! so I think you will have to create 2 templates in this case or you can enable the super set of the components so that authors can use the relevant components in the respective pages.

Thats because, the #3 and #4 are the events that happens in publish instance and hence its in not captured in the servlet in the author mode. Publish the same servlet on the publish instance and see the logs in the publish server

Its always better and recommended to go RESTFUL way via Ajax rather than using iframes.