🫧 Article (JD's) template

[spokanemac]

• [ ] Copy this into the same folder: https://github.com/fleetdm/confidential/blob/main/.github/ISSUE_TEMPLATE/custom-request.md
• [ ] But base it off of this issue
• [ ] Go through the painful questioning from Mike

---
name: 🫧 Article request
about: Propose an article for marketing.
title: 'Article: __________________________'
labels: '#g-marketing'
assignees: ''

---
# Article

## Proposed article title

## Blog Post Summary
<!-- Provide a summary of the proposed blog post. This will help the team 
understand the core message and its value to the readers. //-->

## Goal

<!-- Describe the desired outcome.-->

| User story  |
|:---------------------------------------------------------------------------|
| As a _________________________________________,
| I want to _________________________________________
| so that I can _________________________________________.

>For help creating a user story, see ["Writing a good user 
story"](https://fleetdm.com/handbook/company/development-groups#writing-a-good-user-story) 
in the website handbook.

<details>
  <summary>Technical Details</summary>

- **Blog Post Type**
    - [ ] How-To Guide
    - [ ] Case Study
    - [ ] Interview
    - [ ] Opinion Piece
    - [ ] Research/Insight
    - [ ] Product Update
    - [ ] Other (please specify)
- **Target Audience**
    - [ ] IT Administrators
    - [ ] Security Analysts
    - [ ] Developers
    - [ ] General Audience
- **Targeting Details**
    - [ ] Target Length: <!-- Approximate word count or length for the blog post. -->
    - [ ] Release Date: <!-- Intended blog post publishing date --> 
    - [ ] Draft Due Date: <!-- Deadline for the first draft. It must be one week or more before the Release Date.-->
    - [ ] SEO Keywords: <!-- List keywords to focus on for search engine optimization. -->
    - [ ] SEO Title: <!-- The SEO-friendly title for the blog post. --> 
    - [ ] SEO Description: <!-- Brief blog post description for SEO purposes. --> 
- **TODO**
    - [ ] Author: ( <!-- Person responsible for writing the article. --> )
    - [ ] Proofread for readability/tone: (  )
    - [ ] Technical Reviewer: ( <!-- Person responsible for checking the technical accuracy of the blog post. --> )
    - [ ] Final Art from Design: ( <!-- Person responsible for creating header artwork. --> )
    - [ ] Final Approver: ( <!-- Person responsible for the final approval before publishing. --> )
    - [ ] Merge PR / Publish on website
    - [ ] Field Marketing (@drewbakerfdm): Post on social media
- [ ] 

</details>

## Prerequisites
<-- List any prerequisites that the reader should have before diving into the blog post. -->

## Key Points
<!-- Please list the key points the blog post should cover. This will assist in creating an outline and ensure that all important topics are covered. -->

1. 
2. 
3. 
4. 

## References/Resources
<!-- Provide any external articles, blog posts, or other resources that could help develop this blog post. -->

## Additional Notes
<!-- Please include any additional notes or specifications for the blog post. -->

### [Working Document](https://docs.google.com)

### [Published Link](<!-- https://fleetdm.com/articles/ -->)

[fleet-release]

Proposed blog post shines, Guides, informs, and enlightens, Knowledge growth aligns.

[spokanemac]

https://github.com/fleetdm/fleet/pull/14654 updates/replaces existing release note template.

[Sampfluger88]

@spokanemac Can I get the PR for this? couldn't find it in the history.

[spokanemac]

@Sampfluger88 This was mothballed with the attempt to merge release notes and article requests. Let's discuss this at the next CEO office minutes before I move to a PR.

[Sampfluger88]

@spokanemac Sounds good

[mikermcneil]

• "Plan an article" issue template (based on discussion on Jan 29 office minutes)