diff --git a/.github/ISSUE_TEMPLATE/fleet-article.md b/.github/ISSUE_TEMPLATE/fleet-article.md
new file mode 100644
index 0000000000..4c6a5c8a3a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/fleet-article.md
@@ -0,0 +1,51 @@
+---
+name: 📝 Article
+about: Propose a new article.
+title: 'Article: _________________'
+labels: ':help-marketing'
+assignees: ''
+---
+
+
+<!--
+STEPS TO CREATE A NEW FLEET ARTICLE:
+1. Create a title:
+  a. Start the line with a single (1) # symbol to mark it as an H1 header.
+  b. Add a blank line below the title.
+2. Add your first sentence or paragraph below the new blank line.
+3. Optionally, add paragraph / subsection titles:
+  a. Start the paragraph / subsection title line with two (2) ## symbols to mark it as an H2 header.
+  b. Add a blank line, then, add more text below your paragraph / subsection headers if used.
+4. Optionally, add more stuff:
+  a. To use links, see the different style options here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#links
+  b. To use images or GIFs, see the different style options here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images
+  c. To use code blocks, use back ticks, as described here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code-and-syntax-highlighting
+5. Correctly populate the article metadata at the bottom of your article body.
+6. There are no other style conventions that must be followed - the GitHub markdown specification is available to use as needed.
+7. You can use the text below this comment as an article template:
+-->
+
+# TITLE (# = H1 header)
+
+Lorem ipsum dolor sit amet...
+
+## PARAGRAPH / SUBSECTION TITLE (## = H2 header)
+
+Lorem ipsum dolor sit amet...
+
+[The entire GitHub markdown cheat sheet...](https://www.google.com)
+
+![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 1")
+
+```
+some
+amazing
+program
+```
+
+<meta name="articleTitle" value="YOUR TITLE GOES HERE">
+<meta name="authorFullName" value="YOUR NAME AS IT WILL APPEAR IN THE ARTICLE GOES HERE">
+<meta name="authorGitHubUsername" value="YOUR GITHUB HANDLE GOES HERE">
+<meta name="category" value="THE CATEGORY (WHICH USUALLY SHOULD = GUIDES) GOES HERE">
+<meta name="publishedOn" value="THE DATE (WHICH IS FORMATEED AS YYYY-MM-DD) GOES HERE">
+<meta name="description" value="THE ARTICLE DESCRIPTION GOES HERE">
\ No newline at end of file
diff --git a/handbook/company/go-to-market-groups.md b/handbook/company/go-to-market-groups.md
index abbad0fcc7..176cf56575 100644
--- a/handbook/company/go-to-market-groups.md
+++ b/handbook/company/go-to-market-groups.md
@@ -141,6 +141,11 @@ Original posts on LinkedIn by Fleet employees [can be promoted using the Fleet c
 Fleet uses advertising to spread awareness through a broader audience and foster greater engagement within user communities. The more people actively using Fleet, or contributing, the better Fleet will be.
 
 
+#### Articles
+
+[Create an "📝 Article" issue](https://github.com/fleetdm/fleet/issues/new?template=fleet-article.md) and follow the instructions in the template to propose a new article for Fleet to publish.
+
+
 #### Events
 
 It's important for Fleet to engage at [events](https://docs.google.com/spreadsheets/d/1YQXAX2Q_WnGkAwMYjMbQpV3nbCj7gOBbv7Y0u4twxzQ/edit#gid=1931288160). This provides an opportunity to directly engage with potential users and contributors, build relationships, gather feedback, and create a stronger sense of community and trust.