Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 143

Update README.md (#25151)

Browse source
This commit is contained in:
Sam Pfluger 2025-01-04 12:16:17 -06:00 committed by GitHub
parent 9181ba7053
commit 720d28ddfd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
handbook/demand/README.md
View file

@ -99,14 +99,10 @@ After an account is marked "[Research-ready](https://fleetdm.lightning.force.com
The Head of Marketing is the DRI for deploying Fleet's outward-facing content. The content schedule is settled significantly in advance to provide ample time for strategy and planning. Use the following steps to settle content strategy:
1. Using the [content calendar](https://docs.google.com/spreadsheets/d/1KUMsb5OkAsCBQHGkGnNoj__UCPJ7Vbhk1LaEWGEARsg/edit?gid=1931288160#gid=1931288160), propose the content that Fleet will produce in the current quarter, and the strategy behind that content, including:
- Content type and title (e.g. "Article: Fleet takes bacon to new heights with flying pigs release").
- Create date: The date by which the DRI will start crafting the content.
1. Using the [content calendar](https://docs.google.com/spreadsheets/d/1Hso0LxqwrRVINCyW_n436bNHmoqhoLhC8bcbvLPOs9A/edit?gid=809357993#gid=809357993), propose the content that Fleet will produce in the current quarter, and the strategy behind that content, including:
- Release date: The date by which the content will be complete and finalized.
- Primary buying situation: The intended audience.
- DRI: Person(s) responsible for the project management of this content.
- Author: Person(s) responsible for the creation of this content.
- Related event?: Related community or Fleet event, if any.
- Title (e.g. "Article: Fleet takes bacon to new heights with flying pigs release").
2. Attend a 30m meeting with Fleet's Client Platform Engineer & Community Advocate, CTO, and CEO to review and settle the proposed content.