diff --git a/handbook/company/communications.md b/handbook/company/communications.md index e6d500b839..1f1f665dfb 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -18,35 +18,38 @@ We track competitors' capabilities and adjacent (or commonly integrated) product | Area of responsibility | [DRI](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) | | -------------- | --- | -| Revenue | _See [πŸ‹ Chief Revenue Officer](https://fleetdm.com/handbook/sales#team)_ -| Pricing | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ -| Illustrations | _See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_ -| Website | _See [🌐 Digital Experience team](https://fleetdm.com/handbook/digital-experience#team)_ -| Product marketing (PMM) | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ -| Brand marketing | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ -| Public relations | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ -| Revenue pipeline | _See [🫧 Head of Demand Generation](https://fleetdm.com/handbook/demand#team)_ -| Ads | _See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_ -| Video | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ -| Social media | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ -| Blog | _See [πŸš€ Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_ -| Information technology (IT) | _See [πŸš€ Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_ -| Payroll, bookkeeping, AR/AP | _See [πŸ”¦ Head of Business Operations](https://fleetdm.com/handbook/customer-success#team)_ -| Legal contracts | _See [πŸ”¦ Business Operations team](https://fleetdm.com/handbook/customer-success#team)_ -| Customer renewals | _See [🌦️ VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_ -| Customer deployments | _See [🌦️ Infrastructure Engineer](https://fleetdm.com/handbook/customer-success#team)_ -| Customer support | _See [🌦️ Customer Success team](https://fleetdm.com/handbook/customer-success#team)_ -| Quality assurance (QA) | _See [πŸš€ Engineering team](https://fleetdm.com/handbook/engineering#team)_ -| Features & product adoption | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ -| Feature prioritization | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ +| Revenue | _See [πŸ‹ Chief Revenue Officer](https://fleetdm.com/handbook/sales#team)_ +| Pricing | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ +| Illustrations | _See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_ +| Website | _See [🌐 Digital Experience team](https://fleetdm.com/handbook/digital-experience#team)_ +| Product marketing (PMM) | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ +| Brand marketing | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ +| Public relations | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ +| Revenue pipeline | _See [🫧 Head of Demand Generation](https://fleetdm.com/handbook/demand#team)_ +| Ads | _See [🫧 Demand team](https://fleetdm.com/handbook/demand#team)_ +| Video | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ +| Social media | _See [🫧 Digital Marketing Manager](https://fleetdm.com/handbook/demand#team)_ +| Blog | _See [πŸš€ Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_ +| Information technology (IT) | _See [πŸš€ Client Platform Engineer & Community Advocate](https://fleetdm.com/handbook/engineering#team)_ +| Payroll, bookkeeping, AR/AP | _See [πŸ”¦ Head of Business Operations](https://fleetdm.com/handbook/customer-success#team)_ +| Legal contracts | _See [πŸ”¦ Business Operations team](https://fleetdm.com/handbook/customer-success#team)_ +| Customer renewals | _See [🌦️ VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_ +| Customer deployments | _See [🌦️ Infrastructure Engineer](https://fleetdm.com/handbook/customer-success#team)_ +| Customer support | _See [🌦️ Customer Success team](https://fleetdm.com/handbook/customer-success#team)_ +| Quality assurance (QA) | _See [πŸš€ Engineering team](https://fleetdm.com/handbook/engineering#team)_ +| Features & product adoption | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ +| Feature prioritization | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ | Intentionality of Fleet's interfaces | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ -| Best practices for using Fleet | _See [🦒 Product Design team](https://fleetdm.com/handbook/product-design#team)_ +| Best practices for using Fleet | _See [🦒 Product Design team](https://fleetdm.com/handbook/product-design#team)_ | [API design](https://fleetdm.com/docs/rest-api/rest-api) | _See [🦒 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_ | Structure of the [docs](https://fleetdm.com/docs/get-started/why-fleet) | _See [🌐 Head of Design](https://fleetdm.com/handbook/digital-experience#team)_ -| Product reference documentation | _See [🦒 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_ -| What goes in a release | _See [πŸš€ Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ -| Engineering output and architecture | _See [πŸš€ Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ -| Product development | _See [πŸ›©οΈ Product groups](https://fleetdm.com/handbook/company/product-groups#current-product-groups)_ +| Product introduction docs | _See [πŸ› οΈ CEO responsibilities](https://fleetdm.com/handbook/company/leadership#ceo-responsibilities)_ +| Product deployment docs | _See [πŸš€ Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ +| Product usage docs | _See [🦒 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_ +| Product reference docs | _See [🦒 Rachael Shaw](https://fleetdm.com/handbook/product-design#team)_ +| What goes in a release | _See [πŸš€ Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ +| Engineering output and architecture | _See [πŸš€ Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ +| Product development | _See [πŸ›©οΈ Product groups](https://fleetdm.com/handbook/company/product-groups#current-product-groups)_ ### Docs This page details processes related to maintaining and updating the [Fleet documentation](https://fleetdm.com/docs). @@ -59,6 +62,20 @@ Fleet's goal is to answer every question with a link to the docs and/or result i > Fleet's philosophy on how to write useful documentation is public and open-source: ["Why read documentation?"](https://fleetdm.com/handbook/company/why-this-way#why-read-documentation) +The docs are separated into four categories: + +1. [Get started](https://fleetdm.com/docs/get-started/why-fleet) + +2. [Deploy](https://fleetdm.com/docs/deploy/introduction) + +3. [Using Fleet](https://fleetdm.com/docs/using-fleet/fleet-ui) + +4. Reference +- [Configuration](https://fleetdm.com/docs/configuration/fleet-server-configuration) +- [REST API](https://fleetdm.com/docs/rest-api/rest-api) +- [Data tables](https://fleetdm.com/tables/account_policy_data) +- [Built-in queries](https://fleetdm.com/queries) + ## Fleetdm.com Any change to fleetdm.com follows the same process as [making changes](https://fleetdm.com/handbook/company/product-groups#making-changes) to the core product. To propose a change to Fleet's website [create a website request](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%23g-digital-experience&projects=&template=website-request.md&title=Request%3A+__________________________) on the #g-digital-experience kanban board. @@ -227,8 +244,8 @@ Fleet uses these levels to standardize a commitment to minimal esotericism acros - **"Public":** _(Available to public)_ - _(Confidential - for Fleet eyes only)_ - **"ΒΆ":** _(E-group - Direct reports the the CEO)_ -- **"ΒΆΒΆ":** _(Classified - Founders and BizOps)_ -- **"ΒΆΒΆΒΆ":** _(Founders and board members)_ +- **"ΒΆΒΆ":** _(Classified - CEO, Apprentice, and BizOps)_ +- **"ΒΆΒΆΒΆ":** _(CEO, Apprentice to the CEO, and board members)_ ## Email relays There are [several special email addresses](https://docs.google.com/document/d/1tE-NpNfw1icmU2MjYuBRib0VWBPVAdmq4NiCrpuI0F0/edit#) that automatically relay messages to the appropriate people in Fleet. Each email address meets a minimum response time ("Min RT"), expressed in business hours/days, and has a dedicated, directly responsible individual (DRI) who is responsible for reading and replying to emails sent to that address.