SKAMPI User documentation for new users

There is a lot of hesitancy from new users on how to get SKAMPI up and running. And often, the knowledge on how to do that is passed within teams. With a 'quick start' guide in the developer portal, those instructions can be formalised & harmonised across the train.

Reorganised doc structure visible on landing page of SKAMPI docs: https://developer.skao.int/projects/ska-skampi/en/latest/index.html Clicking on "Getting Started" on above page takes a reader to the Quick Start Guide, which is also the README which is open when going to https://gitlab.com/ska-telescope/ska-skampi Demo slides: https://docs.google.com/presentation/d/1Esdz99v6kxD0H2tuFcNrmibXbyxAZxh8AV6xoZ1XYco/edit? User Survey results: https://docs.google.com/forms/d/e/1FAIpQLSc8_7gPBGL5hmZnj-LyBsaHB4UdPzBhtuqPNYtG1k_exJsB1w/viewanalytics Steps of getting deployment running were added to the Documentation and new README Prerequisites are all listed Links to external and other documentation were added and tested Introduction explains what SKAMPI can/can't do the simple git clone paragraph added helped "finding" SKAMPI for someone already reading the docs, but the problem of finding the documentation persists Where to get help documented in a useful manner The need for explaining how to contribute to the documentation (that was expressed in INS-15) was not addressed in this Enabler, nor was it planned as part of the scope for this work. It is still something that needs to be addressed, and was clearly showcased by the Survey results and risk-raising that clear ownership of the project is lacking. The hope that people will go and read documentation simply because it exists is unfounded. The onus of socialisation of the new documentation will have to remain largely with the social structures provided by SAFe (Sync meetings, Team standups, etc). This was an insight gathered at the Problem Solving Workshop, after the demo showcased newly available documentation.