diff --git a/.github/ISSUE_TEMPLATE/1-bug.md b/.github/ISSUE_TEMPLATE/1-bug.md
new file mode 100644
index 00000000..29923e50
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/1-bug.md
@@ -0,0 +1,36 @@
+---
+name: Bug report
+about: Create a report to help us improve WireViz
+title: "[bug] "
+labels: 'bug'
+assignees: ''
+
+---
+
+<!-- Please add a brief summary of your issue to the title above, after the
+     "[bug]" prefix -->
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+- WireViz version: 
+- Graphviz version (`dot -V`): 
+- Python version: (`python -V`): 
+- Operating System and version: 
+
+**Additional context**
+Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/2-feature.md b/.github/ISSUE_TEMPLATE/2-feature.md
new file mode 100644
index 00000000..8911d778
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/2-feature.md
@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[feature] "
+labels: 'enhancement'
+assignees: ''
+
+---
+
+<!-- Please add a brief summary of your request to the title above, after the
+     "[feature]" prefix -->
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/3-doc.md b/.github/ISSUE_TEMPLATE/3-doc.md
new file mode 100644
index 00000000..3176db02
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/3-doc.md
@@ -0,0 +1,26 @@
+---
+name: Documentation issue template
+about: Help us improve the WireViz documentation
+title: "[doc] "
+labels: 'documentation'
+assignees: ''
+
+---
+<!-- Please add a brief summary of your issue to the title above, after the
+     "[doc]" prefix -->
+
+**What documentation page(s) does this involve?**
+Links to the relevant documentation files, e.g. [docs/README.md][].
+
+**Describe the problem**
+A clear and concise description of the documentation issue.
+
+**Describe your suggested improvement**
+A clear and concise summary of how the documentation could be better.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.
+
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 00000000..b92c70cb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,2 @@
+blank_issues_enabled: true
+
diff --git a/.github/issue_template.md b/.github/issue_template.md
new file mode 100644
index 00000000..17cec5f5
--- /dev/null
+++ b/.github/issue_template.md
@@ -0,0 +1,11 @@
+<!-- Where appropriate, prefix your issue title with one of these
+     category prefixes, followed by a space:
+
+     [internal] - When suggesting code improvements that don't change
+                  any output.
+     [meta] - For issues about the development or contribution process.
+
+     For [bug], [feature], or [doc] issues, please use the corresponding
+     issue templates if possible, as they provide more guidance on what
+     information to include. -->
+