Reworking Swarm-Guide API Documentation

[FantasticoFox]

• Currently the documentation is scattered and incomplete.
• Also the status of the API's is not documented.
• No single-entry-point for the CLI / API Documentation.

Delivery: This required for the EF-MVP-Clarification
Time 15th of June latest. Sooner is better :)

Target Release 0.4.2

[acud]

@FantasticoFox Can you please elaborate on what drew you to the following conclusions about our documentation? we have completely revised our entire documentation on several iterations, in a very thorough way to the point we have almost no community overhead asking basic questions on "how to do this or that" over gitter all the time.
Is this just your personal opinion or have you come to this conclusion from using other people's opinions too? I'm just curious to know based on what assumptions are we dismissing the huge amount of work that was done here

[adamschmideg]

The idea is we'll have two types of documentation. The Swarm guide is intended for those who want to understand everything from architecture to the nitty-gritty details. It serves that purpose perfectly well. The document to be written is meant for developers who want to get onboard as fast as possible. Imagine a hackathon when you have ten minutes to get up and running. This latter documentation is to cherrypick from the more thorough Swarm guide.