033be67742
point to https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility (mostly because this section is what comes up in algolia search if you search the handbook for "DRI"-- this way there's a kind of breadcrumb to the explanation. But always nice to unfold acronyms anyways)
4.3 KiB
How to submit and publish an article
This guide includes everything you need to know about Fleet’s editorial process between submission and publication.
For help with formatting your article, check out our article formatting guide.
Article DRIs
| Activity | DRI |
|---|---|
| Assign | Jarod Reyes |
| Review | Jarod Reyes |
| Artwork | Mike Thomas |
| Schedule & Publish | Drew Baker |
What is a DRI?
Who can publish articles?
Everyone is welcome to suggest article ideas or submit drafts. Reach out to Jarod Reyes in #help-content-calendar on Slack, and include a summary of your idea in the thread.
Communication
Use the #help-content-calendar channel in Slack for questions and updates related to articles.
Schedule
Publishing occurs according to our content calendar. However, publication dates are subject to change based on the news or information that needs to be posted. For time-sensitive articles, consult with Jarod Reyes in #help-content-calendar on Slack.
How to submit an article
- Submit your draft to Jarod Reyes as a Google Doc.
- Include any relevant images, image suggestions, or other design requests you may have.
Review process
Articles are official Fleet communication. We carefully review published content to make sure Fleet, the company and the product, are accurately represented.
- Digital Experience will review your article for spelling, punctuation, and grammar, as well as for tone and brand consistency.
- In some cases, a technical review by a member of Engineering or Security may be necessary.
- After review, you may be asked to make revisions to your draft.
Typical editing timelines are as follows:
| Type | Review time |
|---|---|
| Urgent posts | One business day |
| Non-urgent posts | Three business days |
| Posts requiring a technical review | Three business days |
Review times for posts requiring a technical review may vary depending on the Engineering and Security teams' schedules. E.g., if a review coincides with a product release.
Create a PR for your article
After your article has been editied and approved, create a pull request on fleetdm.com and request review from Jarod Reyes.
How to PR your article
- Familiarize yourself with our article formatting guide.
- Add a file, formatted in Markdown, to the Fleet repo in Github fleetdm/fleet/articles, using the name of your article as the filename. E.g.,
deploy-fleet-on-render.md. - Request a review from Jarod Reyes.
Important
: Your PR is not confidential. If the information in your article is confidential, please prepare your article in a Google Doc, or create a draft PR ~1 hour before publication time to keep your article private.
Pre-publication checklist
- Does the article meet the original brief and keyword goals?
- Has the article been reviewed by Digital Experience for grammar edits and brand consistency?
- Does the article require a technical review?
- Do all links work correctly and open in a new window?
- Does the article contain the correct meta tags
- Has artwork been created by Digital Experience?
- Does the article have a clear call to action (CTA)?
After publication
After your article is published, the Growth team will schedule your post to be promoted across our social media channels.
Consider promoting your article on your personal channels to help achieve a bigger impact. Depending on the article, the Growth team may make a request in #help-promote on Slack.