New documentation structure

[cakrit]

Restructure tree as follows:

Guides

• Welcome Guide
• Installation Guide
• Configuration Guide
• Tuning Guide
• Systems Monitoring Reference
• Applications Monitoring Reference (could be a automatically generated, interactive)
• APM (statsd)
• Metrics Streaming & Replication
• Metrics Archiving (backends)
• Health Monitoring & Notifications
• Alarms Reference (could be automatically generated, interactive)
• Netdata Registry
• APIs Reference (data collection, web API, etc)
• Custom Dashboards & Badges (including reference for each chart library we use)
• Development Guide (write plugins, protocols used, APIs, etc)

How To:

• Monitoring web servers
• Netdata with Prometheus
• Monitoring Ephemeral Nodes
• Monitoring Kubernetes
• Monitoring Containers and Virtual Machines
• Monitoring an IoT cloud
• Monitoring the process tree with netdata
• Visual Anomaly Detection with netdata

[cakrit]

I structured the content differently, trying to follow the way atom does it. The current draft can be seen at https://netdata.netlify.com
We definitely need:

• Better separation of user and developer documentation
• Get impressions/suggestions