mirror of
https://github.com/fleetdm/fleet
synced 2026-05-04 05:48:26 +00:00
f2df737a0b
<ins>*🌐 IT and Enablement:*</ins> - Rename "🌐 Digital Experience" to "🌐 IT and Enablement" dept - Rename "digital-experience.rituals.yml" to "it-and-enablement.rituals.yml" <ins>*🧑🚀 People*</ins> - Create 🧑🚀 People dept - Create "people.rituals.yml" <ins>*🔭 CEO*</ins> (<= WHY? To maintain the [structure of the handbook](https://fleetdm.com/handbook/company/leadership#outline-of-departmental-page-structure).) - Create 🔭 CEO page and link to leadership - Create ceo.rituals.yml <ins>*💸 Finance*</ins> - Renamed label "#g-finance" to ":help-finance" to match the rest of the departmental labels. --------- Co-authored-by: Eric <eashaw@sailsjs.com>
51 lines
2.1 KiB
Markdown
51 lines
2.1 KiB
Markdown
---
|
|
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)
|
|
|
|
|
|
|
|
```
|
|
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">
|