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

Handbook: Blog post publishing process (#2299)

Browse source 
* Update growth.md

Added a section for Fleet blog post authors about how to promote their blog posts to our social media.

Some thoughts. Including an assignee is not very future proof, in case roles change etc. Maybe best to leave that out, and we can add an assignee when we see the issue in Growth meetings.

HackerNews reserved for release posts only. Added that based on recent recommendation, due to HackerNew's strict policies. Are we happy with that, or should promoting on HackerNews be treated case-by-case?

* Update growth.md

* Update growth.md

* Update growth.md

* Update growth.md
This commit is contained in:
Mike Thomas 2021-09-30 12:13:03 +09:00 committed by GitHub
parent d3a2083188
commit e3ff9e4274
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
handbook/growth.md
View file

@ -1,3 +1,7 @@
## Promoting blog posts on social media
Once a blog post has been written, approved, and published, please ensure that it has been promoted on social media. Please refer to our [Publishing as Fleet](https://docs.google.com/document/d/1cmyVgUAqAWKZj1e_Sgt6eY-nNySAYHH3qoEnhQusph0/edit?usp=sharing) guide for more detailed information.
## Fleet website
@ -50,14 +54,6 @@ or
> Osquery and Fleet provide structured, convenient access to information about your devices.
## Culture
### All remote
Fleet Device Management Inc. is an all-remote company, with team members spread across 3 continents and 5 time zones. The wider team of contributors from [all over the world](https://github.com/fleetdm/fleet/graphs/contributors) submit patches, bug reports, troubleshooting tips, improvements, and real-world insights to Fleet's open source code base, documentation, website, and company handbook.
### Openness
The majority of the code, documentation, and content we create at Fleet is public and source-available, and we strive to be broadly open and transparent in the way we run the business; as much as confidentiality agreements (and time) allow. We perform better with an audience, and our audience performs better with us.