diff --git a/.github/ISSUE_TEMPLATE/content-bug.md b/.github/ISSUE_TEMPLATE/content-bug.md
new file mode 100644
index 000000000000000..bc0f4579ca34822
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/content-bug.md
@@ -0,0 +1,33 @@
+---
+name: Content bug
+about: "Use this template to notify us of a content bug that needs fixing"
+labels: "needs-triage"
+assignees:
+title: "Content bug:
"
+---
+
+## What page(s) did you find the problem on?
+
+
+
+## Specific page section or heading?
+
+
+
+## What is the problem?
+
+
+
+## What did you expect to see?
+
+
+
+## Did you test this? If so, how?
+
+
diff --git a/.github/ISSUE_TEMPLATE/new-content-suggestion.md b/.github/ISSUE_TEMPLATE/new-content-suggestion.md
new file mode 100644
index 000000000000000..4b6ccb5e9fae523
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/new-content-suggestion.md
@@ -0,0 +1,27 @@
+---
+name: New content suggestion
+about: "Use this template to suggest new larger areas of work that you think the MDN writers should work on"
+labels: "Opportunity assessment",
+assignees: chrisdavidmills
+title: "Content suggestion: "
+---
+
+## What is the new suggestion?
+
+
+## Why is it important or useful?
+
+
+## Other supporting information
+
+
diff --git a/.github/PULL_REQUEST_TEMPLATE b/.github/PULL_REQUEST_TEMPLATE
new file mode 100644
index 000000000000000..0a20d04af8113aa
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE
@@ -0,0 +1,6 @@
+Checklist — To help your pull request get merged faster, please do following:
+
+1. - [ ] Provide a summary of your changes — say what problem you are fixing, what files are changed, what you've done. This doesn't need to be hugely detailed, as we can see exact changes in the "Files changed" tab.
+1. - [ ] Provide a link to the issue(s) you are fixing, if appropriate, in the form "Fixes ". GitHub will render this in the form "Fixes #1234", with the issue number linked to the issue. Doing this allows us to figure out what issues you are fixing, as well as helping to automate things (for example the issue will be closed once the PR that fixed it has been merged).
+1. - [ ] Review the results of the automated checking we run on every PR and fix any problems reported (see the list of checks near the bottom of the PR page). If you need help, please ask in a comment!
+1. - [ ] Link to any other resources that you think might be useful in reviewing your PR.