Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Create article issue template (#28040)

Browse source
This commit is contained in:
Sam Pfluger 2025-04-10 17:55:40 -05:00 committed by GitHub
parent 82c0491b51
commit 6d0c49d70f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 56 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

51
.github/ISSUE_TEMPLATE/fleet-article.md vendored Normal file
View file

@ -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">

5
handbook/company/go-to-market-groups.md
View file

@ -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.