From 587509ec7857e091798370fbac25ea41971607bd Mon Sep 17 00:00:00 2001
From: Endilie Yacop Sucipto <endiliey@gmail.com>
Date: Fri, 6 Jul 2018 13:55:18 +0800
Subject: [PATCH] Better issue templates (#833)

* Use github template for new issue

* Update bug.md

* Update feature.md

* Update proposal.md

* Update question.md

* Update CONTRIBUTING.md
---
 .github/ISSUE_TEMPLATE.md          | 86 +-----------------------------
 .github/ISSUE_TEMPLATE/bug.md      | 61 +++++++++++++++++++++
 .github/ISSUE_TEMPLATE/feature.md  | 30 +++++++++++
 .github/ISSUE_TEMPLATE/proposal.md | 12 +++++
 .github/ISSUE_TEMPLATE/question.md | 14 +++++
 CONTRIBUTING.md                    |  8 +--
 6 files changed, 123 insertions(+), 88 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug.md
 create mode 100644 .github/ISSUE_TEMPLATE/feature.md
 create mode 100644 .github/ISSUE_TEMPLATE/proposal.md
 create mode 100644 .github/ISSUE_TEMPLATE/question.md

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 28bdfafdad..c7c7b52fe2 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -1,85 +1,3 @@
-<!--
-  PLEASE DON'T DELETE THIS TEMPLATE UNTIL YOU HAVE READ THE FIRST SECTION.
--->
+## 👉 [Please follow one of these issue templates](https://github.com/facebook/Docusaurus/issues/new/choose) 👈
 
-### Is this a bug report?
-
-(write your answer here)
-
-<!--
-  If you answered "Yes":
-
-    We expect that it will take you about 10-30 minutes to produce a high-quality bug report.
-    While this may seem like a lot, putting care into issues helps us fix them faster.
-    For bug reports, it is REQUIRED to fill the rest of this template, or the issue will be closed.
-
-  If you answered "No":
-
-    We use GitHub Issues exclusively for tracking bugs and feature requests in Docusaurus. If you're looking for help,
-    the Docusaurus Twitter account, @docusaurus, can be used for help.
-
-  Now scroll below!
--->
-
-### Have you read the [Contributing Guidelines on issues](https://github.com/facebook/Docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues)?
-
-(Write your answer here.)
-
-### Environment
-
-(Docusaurus version via `npm outdated docusaurus` or `yarn outdated docusaurus`, OS, Node, npm, yarn)
-
-### Steps to Reproduce
-
-<!--
-  How would you describe your issue to someone who doesn’t know you or your project?
-  Try to write a sequence of steps that anybody can repeat to see the issue.
-  Be specific! If the bug cannot be reproduced, your issue may be closed.
--->
-
-(Write your steps here:)
-
-1.
-2.
-3.
-
-### Expected Behavior
-
-<!--
-  How did you expect your project to behave?
-  It’s fine if you’re not sure your understanding is correct.
-  Just write down what you thought would happen.
--->
-
-(Write what you thought would happen.)
-
-### Actual Behavior
-
-<!--
-  Did something go wrong?
-  Is something broken, or not behaving as you expected?
-  Describe this section in detail, and attach screenshots if possible.
-  Don't just say "it doesn't work"!
--->
-
-(Write what happened. Add screenshots, if applicable.)
-
-### Reproducible Demo
-
-(Paste the link to an example repo, including a `siteConfig.js`, and exact instructions to reproduce the issue.)
-
-<!--
-  What happens if you skip this step?
-
-  Someone will read your bug report, and maybe will be able to help you,
-  but it’s unlikely that it will get much attention from the team. Eventually,
-  the issue will likely get closed in favor of issues that have reproducible demos.
-
-  Please remember that:
-
-    * Issues without reproducible demos have a very low priority.
-    * The person fixing the bug would have to do that anyway. Please be respectful of their time.
-    * You might figure out the issues yourself as you work on extracting it.
-
-  Thanks for helping us help you!
--->
+Note: to keep the backlog clean and actionable, issues may be immediately closed if they do not follow one of the above issue templates.
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
new file mode 100644
index 0000000000..618eb73ce4
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -0,0 +1,61 @@
+---
+name: 🐛 Bug Report
+about: Submit a bug report to help us improve
+---
+
+## 🐛 Bug Report
+
+(A clear and concise description of what the bug is)
+
+### Have you read the [Contributing Guidelines on issues](https://github.com/facebook/Docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues)?
+
+(Write your answer here.)
+
+## To Reproduce
+
+(Write your steps here:)
+
+1.
+2.
+3.
+
+## Expected behavior
+
+<!--
+  How did you expect your project to behave?
+  It’s fine if you’re not sure your understanding is correct.
+  Just write down what you thought would happen.
+-->
+
+(Write what you thought would happen.)
+
+## Actual Behavior
+
+<!--
+  Did something go wrong?
+  Is something broken, or not behaving as you expected?
+  Describe this section in detail, and attach screenshots if possible.
+  Don't just say "it doesn't work"!
+-->
+
+(Write what happened. Add screenshots, if applicable.)
+
+## Reproducible Demo
+
+(Paste the link to an example repo, including a `siteConfig.js`, and exact instructions to reproduce the issue.)
+
+<!--
+  What happens if you skip this step?
+
+  Someone will read your bug report, and maybe will be able to help you,
+  but it’s unlikely that it will get much attention from the team. Eventually,
+  the issue will likely get closed in favor of issues that have reproducible demos.
+
+  Please remember that:
+
+    * Issues without reproducible demos have a very low priority.
+    * The person fixing the bug would have to do that anyway. Please be respectful of their time.
+    * You might figure out the issues yourself as you work on extracting it.
+
+  Thanks for helping us help you!
+-->
diff --git a/.github/ISSUE_TEMPLATE/feature.md b/.github/ISSUE_TEMPLATE/feature.md
new file mode 100644
index 0000000000..af992e3d02
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature.md
@@ -0,0 +1,30 @@
+---
+name: 🚀 Feature
+about: Submit a proposal/request for a new feature
+---
+
+## 🚀 Feature
+
+(A clear and concise description of what the feature is)
+
+## Have you read the [Contributing Guidelines on issues](https://github.com/facebook/Docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues)?
+
+(Write your answer here.)
+
+## Motivation
+
+(Please outline the motivation for the proposal)
+
+## Pitch
+
+(Please explain why this feature should be implemented and how it would be used)
+
+<!--
+  What happens if you skip this step?
+
+  Someone will read your feature proposal and maybe will be able to help you,
+  but it’s unlikely that it will get much attention from the team. Eventually,
+  the issue will likely get closed in favor of issues that have better explanations
+
+  Thanks for helping us help you!
+-->
diff --git a/.github/ISSUE_TEMPLATE/proposal.md b/.github/ISSUE_TEMPLATE/proposal.md
new file mode 100644
index 0000000000..2c3814af2e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/proposal.md
@@ -0,0 +1,12 @@
+---
+name: 💥 Proposal
+about: Propose a non-trivial change to Docusaurus
+---
+
+## 💥 Proposal
+
+(A clear and concise description of what the proposal is.)
+
+### Have you read the [Contributing Guidelines on issues](https://github.com/facebook/Docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues)?
+
+(Write your answer here.)
diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
new file mode 100644
index 0000000000..bc88230c02
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/question.md
@@ -0,0 +1,14 @@
+---
+name: 💬 Questions/Help
+about: If you have questions, please check StackOverflow or Discord or Twitter
+---
+
+## 💬 Questions and Help
+
+### Please note that this issue tracker is not a help form and this issue will be closed.
+
+Please contact us instead. We have a few channels:
+
+- [Stack Overflow](https://stackoverflow.com/questions/tagged/docusaurus)
+- [Twitter](https://twitter.com/docusaurus)
+- [Discord](https://discord.gg/docusaurus)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 943ee229f4..9cc00f275c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -51,11 +51,11 @@ We use [GitHub Issues](https://github.com/facebook/docusaurus/issues) for our pu
 
 If you have questions about using Docusaurus, contact the Docusaurus Twitter account at [@docusaurus](https://twitter.com/docusaurus), and we will do our best to answer your questions.
 
-You can also file issues as [feature requests or enhancements](https://github.com/facebook/docusaurus/labels/enhancement). If you see anything you'd like to be implemented, create an issue and label it as `enhancement`.
+You can also file issues as [feature requests or enhancements](https://github.com/facebook/Docusaurus/labels/feature%20request). If you see anything you'd like to be implemented, create an issue with [feature template](https://raw.githubusercontent.com/facebook/docusaurus/master/.github/ISSUE_TEMPLATE/feature.md)
 
 ## Reporting new issues
 
-When [opening a new issue](https://github.com/facebook/docusaurus/issues/new), always make sure to fill out the [issue template](https://raw.githubusercontent.com/facebook/docusaurus/master/.github/ISSUE_TEMPLATE.md). **This step is very important!** Not doing so may result in your issue not managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
+When [opening a new issue](https://github.com/facebook/docusaurus/issues/new/choose), always make sure to fill out the issue template. **This step is very important!** Not doing so may result in your issue not managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
 
 * **One issue, one bug:** Please report a single bug per issue.
 * **Provide reproduction steps:** List all the steps necessary to reproduce the issue. The person reading your bug report should be able to follow these steps to reproduce your issue with minimal effort.
@@ -78,9 +78,9 @@ We have a list of [beginner friendly issues](https://github.com/facebook/docusau
 
 ### Proposing a change
 
-If you would like to request a new feature or enhancement but are not yet thinking about opening a pull request, you can also file issues as [feature requests or enhancements](https://github.com/facebook/docusaurus/labels/enhancement)..
+If you would like to request a new feature or enhancement but are not yet thinking about opening a pull request, you can also file an issue with [feature template](https://github.com/facebook/docusaurus/issues/new?template=feature.md).
 
-If you intend to change the public API (e.g., something in `siteConfig.js`), or make any non-trivial changes to the implementation, we recommend [filing an issue](https://github.com/facebook/docusaurus/issues/new?title=%5BProposal%5D) that includes `[Proposal]` in the title. This lets us reach an agreement on your proposal before you put significant effort into it. These types of issues should be rare.
+If you intend to change the public API (e.g., something in `siteConfig.js`), or make any non-trivial changes to the implementation, we recommend filing an issue with [proposal template](https://github.com/facebook/docusaurus/issues/new?template=proposal.md) and including `[Proposal]` in the title. This lets us reach an agreement on your proposal before you put significant effort into it. These types of issues should be rare.
 
 If you're only fixing a bug, it's fine to submit a pull request right away but we still recommend to file an issue detailing what you're fixing. This is helpful in case we don't accept that specific fix but want to keep track of the issue.