Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 01:18:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 84

Handbook - publishing Fleet content (#6051)

Browse source 
* Digital Experience services

Added a table for Digital Experience service requests.

* Update brand.md

Updated text

* text change

Changes "with the contributor" to "to the contributor".

* Update brand.md

Updated table and introduction.

* Update brand.md

text change

* Update .sailsrc

Omitted changes that were accidentally pushed.

Co-authored-by: Eric <eashaw@sailsjs.com>
This commit is contained in:
Mike Thomas 2022-06-07 12:14:55 +09:00 committed by GitHub
parent 8b3a3e2eca
commit 0ffd4638f9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 38 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
handbook/brand.md
View file

@ -1,5 +1,43 @@
# Brand
## Publishing Fleet content
The following describes how to go about publishing and editing content at Fleet.
### Publication methods
1. **Instant**: Content is published instantly. Content is approved by Digital Experience post-facto – see links in the table below to get the required training.
2. **Gated**: Submit content to Digital Experience for review – see specific instructions in the table below.
3. **Queued**: Communicate the publication date with the [DRI](https://fleetdm.com/handbook/people#directly-responsible-individuals) responsible for approving this content – refer to specific instructions linked in the table below.
### Revision methods (for editors)
1. **Absorb**: Fix and publish yourself
2. **Feedback**: Request changes and wait
3. **Pairing**: Jump on Zoom to finalize with the original contributor.
> Consider: **Absorb** may be risky depending on how sure the editor is about their edits. **Feedback** can get forgotten about. **Pairing** is underused, but can eat up more time, if not careful.
### Timeframe
Details the minimum time needed for new or updated content to be live (published) and brand-approved (reviewed and revised, if necessary).
### Content types
| Content | To publish | To revice (for editors) | Timeframe |
|:------ |:-----------------|:-------------------------------|-----------|
| Articles | **Queued** – see _(TODO: Publishing articles on fleetdm.com)_. | **Absorb** (pair or feedback as needed) – see [How to edit articles, release posts, and press releases](http://localhost:2024/handbook/brand#how-to-edit-articles-release-posts-and-press-releases). | 3 business days |
| Ads | **Gated**. Request review from Digital Experience – see _(TODO: Creating an ad campaign)_. | **Feedback** or **pair** | 5 business days |
| Docs | **Gated**. Request review from Noah Talerman – see _(TODO: Adding to the docs)_. | **Absorb** – see [How to edit recently merged Pull Requests for the handbook and docs](http://localhost:2024/handbook/brand#how-to-edit-recently-merged-pull-requests-for-the-handbook-and-docs). For non-grammar-related revisions: **Feedback** or **pair** with contributor, and request review from Noah Talerman. | 2 business days |
| Docs (REST API) | **Gated**. Request review from Luke Heath – see _(TODO: Adding to the docs (REST API))_. | **Absorb** – see [How to edit recently merged Pull Requests for the handbook and docs](http://localhost:2024/handbook/brand#how-to-edit-recently-merged-pull-requests-for-the-handbook-and-docs). For non-grammar-related revisions: **Feedback** or **pair** with contributor, and request review from Luke Heath. | 2 business days |
| Handbook | **Gated**. Request review from page DRI – see _(TODO: Adding to the handbook)_. | **Absorb** and request review from page DRI – see see [How to edit recently merged Pull Requests for the handbook and docs](http://localhost:2024/handbook/brand#how-to-edit-recently-merged-pull-requests-for-the-handbook-and-docs). | 2 business days |
| Social media (Twitter, FB, LinkedIn.) | **Instant** – see [Posting on social media as Fleet](https://fleetdm.com/handbook/growth#posting-on-social-media-as-fleet). | **Pair** or **absorb** (pair if possible, otherwise silently fix ASAP by editing or deleting the post. Consider that some or many people may have already seen the post, and decide accordingly – see [How to edit social media posts](http://localhost:2024/handbook/brand#how-to-edit-social-media-posts).) | 1 business day |
| Newsletter/email blast | **Gated**. Request review from Digital Experience – see _(TODO: Creating an email campaign)_. | **Feedback** or **pair** | 5 business days |
| Press release | **Queued** – see _(TODO: Publishing a press release)_ | **Feedback** or **pair** – see [How to edit articles, release posts, and press releases](http://localhost:2024/handbook/brand#how-to-edit-articles-release-posts-and-press-releases) | 3 business days |
| Release post | **Queued** – see _(TODO: Publishing release posts)_ | **Feedback** or **pair** – see [How to edit articles, release posts, and press releases](http://localhost:2024/handbook/brand#how-to-edit-articles-release-posts-and-press-releases) | 3 business days |
| Website (text change) | **Gated** – see _(TODO: Adding content to fleetdm.com)_. | **Feedback** or **pair** | 3 business days |
| YouTube | **Queued** – see _(TODO: Publishing on YouTube as Fleet.)_ | **Absorb** for revisions to the description. **Pair** or **absorb** for video content (pair if possible, otherwise silently fix ASAP by deleting the post. Consider that the video may also have been promoted on social media – see Social media (Twitter, FB, LinkedIn) above. | 3 business days |
## Communicating as Fleet
- **Sound positive** and assume positive intent. A positive tone helps to empower our users and encourages them to succeed with Fleet.