Updated issue templates

[ci skip]

.github/ISSUE_TEMPLATE.md

@@ -1,31 +0,0 @@
-## Issue Checklist
-
-Before creating a new issue make sure that you
-- searched existing (and closed) issues: https://github.com/cryptomator/cryptomator/issues
-- searched the knowledge base: https://community.cryptomator.org/c/kb
-- have read the support guide: https://github.com/cryptomator/cryptomator/blob/develop/SUPPORT.md
-- have read the contribution guide: https://github.com/cryptomator/cryptomator/blob/develop/.github/CONTRIBUTING.md
-- have read the code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
-
-## Basic Info
-
-I'm using Windows / macOS / Linux / … in version: …
-
-I'm running Cryptomator in version: …  
-(You can check the version in the Cryptomator settings.)
-
-## Description
-
-…  
-(Please describe in detail what you did, what you expected, and what really happened.)
-
-## Attachments (optional)
-
-If you want to add the log file or screenshots, please add them as attachments. If your log file seems empty and doesn't show any errors, you may enable the debug mode first. Here is how to do that: https://community.cryptomator.org/t/how-do-i-enable-debug-mode/36
-
-Then reproduce the problem to ensure all important information is contained in there. You may use test data or redact sensitive information from the log file.
-
-You can find the log file
-- on Windows: %appdata%/Cryptomator/cryptomator.log
-- on macOS: ~/Library/Logs/Cryptomator/cryptomator.log
-- on Linux: ~/.Cryptomator/cryptomator.log

.github/ISSUE_TEMPLATE/1.4.0-beta-testing.md

@@ -1,15 +0,0 @@
-## 1.4.0 Beta Issue Checklist
-- Existing 1.4.0 Beta Issues: https://github.com/cryptomator/cryptomator/milestone/27
-- Contribution Guide: https://github.com/cryptomator/cryptomator/blob/develop/.github/CONTRIBUTING.md
-- Code of Conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
-
-## Software Used During the Test
-- Cryptomator 1.4.0 Beta 1
-- Ubuntu 16.04 / macOS 10.11.6 / etc
-- Linux Kernel x.y.z
-- Gnome x.y.z
-- OpenOffice x.y.z
-- ...
-
-## Description
-What doesn't work? What did you do? How can the bug be reproduced?

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,56 @@
+---
+name: "Bug Report"
+about:  "Create a report to help us improve"
+labels: type:bug
+---
+
+<!--
+
+Do you want to ask a QUESTION? Are you looking for SUPPORT?
+We're happy to help you via our support channels! Please read: https://github.com/cryptomator/cryptomator/blob/develop/SUPPORT.md
+
+By filing an issue, you are expected to comply with our code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
+
+Of course we also expect you to search for existing similar issues, first! ;) https://github.com/cryptomator/cryptomator/issues?q=
+
+-->
+
+### Description
+
+[Summarize your problem]
+
+### System Setup
+
+* Operating system and version:
+* Cryptomator version (shown in the settings):
+* Drive (FUSE/Dokany/WebDAV):
+
+### Steps to Reproduce
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+#### Expected behavior:
+[What you expect to happen]
+
+#### Actual behavior
+[What actually happens]
+
+#### Reproduces how often:
+[What percentage of the time does it reproduce?]
+
+### Additional Information
+
+Any additional information, log files, screenshots, configuration or data that might be necessary to reproduce the issue.
+
+<!--
+If you want to add the log file or screenshots, please add them as attachments. If your log file seems empty and doesn't show any errors, you may enable the debug mode first. Here is how to do that: https://community.cryptomator.org/t/how-do-i-enable-debug-mode/36
+
+Then reproduce the problem to ensure all important information is contained in there. You may use test data or redact sensitive information from the log file.
+
+You can find the log file
+- on Windows: %appdata%/Cryptomator/cryptomator.log
+- on macOS: ~/Library/Logs/Cryptomator/cryptomator.log
+- on Linux: ~/.Cryptomator/cryptomator.log
+-->

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,32 @@
+---
+name: "Feature Request"
+about:  "Suggest an idea for this project"
+labels: type:feature-request
+---
+
+<!--
+
+Do you want to ask a QUESTION? Are you looking for SUPPORT?
+We're happy to help you via our support channels! Please read: https://github.com/cryptomator/cryptomator/blob/develop/SUPPORT.md
+
+By filing a feature request, you are expected to comply with our code of conduct: https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md
+
+Of course we also expect you to search for existing similar feature requests, first! ;)
+
+-->
+
+### Summary
+
+One paragraph explanation of the feature.
+
+### Motivation
+
+Why are we doing this? What use cases does it support? What is the expected outcome?
+
+### Describe alternatives you've considered
+
+A clear and concise description of the alternative solutions you've considered. Be sure to explain why Atom's existing customizability isn't suitable for this feature.
+
+### Additional context
+
+Add any other context or screenshots about the feature request here.

SUPPORT.md

@@ -4,7 +4,15 @@ For development-related topics, GitHub is the right place.
 
 For _everything else_, please visit our official [Cryptomator Community](https://community.cryptomator.org) (we are there, too :wink:). Amongst others, you will find:
 
-- Installation manuals
-- Usage guides
-- Help with problems
-- Tips & tricks
+- [Knowledge Base](https://community.cryptomator.org/c/kb)
+  - Installation manuals
+  - Usage guides
+  - FAQ
+- [Help with problems](https://community.cryptomator.org/c/help)
+  - Assistance with the setup
+  - Known issues and workarounds
+  - Discussions about the apps
+- [Development discussions](https://community.cryptomator.org/c/development)
+  - General questions
+  - Discussions regarding our design decissions
+  - Our roadmap