Yes, I know: documentation is a mess.
Well, I think there should be documentation in the following structure.
One way to do it, is to open a new github repo to put all documentation there and then replace the wiki of this repo with the new one. For this to work, this has to be quick (otherwise the 2 wikis will get out of sync pretty quickly).
If you are willing to help me out, please join.
FreeBSD will more than likely have netdata in ports (package repo) once there's a release.
It's also listed in Wanted Ports. https://wiki.freebsd.org/WantedPorts
This replaces #378.
The table of contents you posted above looks good. Some thoughts of the old thread:
@ktsaou just reminder, if deciding to create new repo, wiki has git url so you can clone to keep the history from wiki's git:
git clone https://github.com/firehol/netdata.wiki.git
git remote add newrepo https://github.com/firehol/docs.git
actually same applies if deciding to merge with netdata repo, just need to use --allow-unrelated-histories option to git merge, and perhaps even git filter-branch to mv to subdir files
thanks! I am already keeping a backup of the wiki every few minutes and I am receiving alarms when pages are edited (better be safe than sorry...)