markdown guide

If there's an issue template, follow the damn thing.

This is seriously my number one complaint as someone who triages issues for Netdata. We have a set of issue templates, but it's not unusual for somebody who isn't part of the team and can't prove that it makes sense to just nuke the template and write a free-form issue description, and then I (or whoever else is triaging the issue) end up having to go back and forth with the person who reported the issue half a dozen times just to get the info we would have had if they had followed the issue template.


A short explanation that serves as a TLDR. And a long detailed one, but let it be spaced out and simply readable.