Incorporated changes discussed at CEO office hour into SLA chart.
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
* Add critical policies to pricing page
- Add "Mark issues as critical" for critical policies feature (Premium only)
- Feature will be included in the upcoming 4.25.0 release
- Move "Detect and surface issues with devices" above "Mark issues" as critical
* Update pricing-features-table.yml
* Add "(policies)"
* Update why-this-way.md
These edits address items 6 and 9 from the handbook notes doc: https://docs.google.com/document/d/17BhgTqCI5255RY71m5ri3nDx71DqmfYwyJmRe_nJ4Ns/edit?usp=sharing.
The content for Why open source? identifies benefits and addresses security concerns. I ended this section with a sort of call to action. This differs from other content in Why this way, but it seemed like a good opportunity. If this feels too aggressive, I can cut the Results section.
I've consolidated the bullets for every company values, as well as wrote summaries for the values that didn't have them. The goal is to make each value more distinct and easier to understand.
* Update README.md
* Update README.md
* Update pricing-features-table.yml
* It doesn't actually support markdown, I just got excited
* Add features key to device management category
* Apply suggestions from code review
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
* Mark profiles as free
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Mo Zhu <mo@fleetdm.com>
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
* Handbook: Openness value
adding the Q&A session to the "why this way" page
* Update handbook/company/why-this-way.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update why-this-way.md
I revised the copy Charlie provided for two main reasons.
First, to keep formatting on the page consistent by removing the Q&A framework.
Second, to apply Mike's rationale from the Slack conversation to speak about Openness more broadly. People who find this section won't have the Slack conversation for context. Stepping back a bit will make this more approachable. However, I'm happy to add more detail if necessary.
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Updated Fleet style guide
Updated style guide and added it to a subpage.
* Fixed a couple of blockquote formatting issues
* removed h4 example
* Implementing Mike's revisions.md
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Updated handbook to reflect merge of help-brex-memos and help-travel Slack channels into help-brex channel, and for reaching out in g-business-operations for non-travel Brex purchases that would exceed a cardholder's monthly limit.
* update navigation
## The problem
After consolidating Growth, Community, and Digital Experience (Brand) under "Marketing", the side navigation has become overwhelming and unclear what sections falls into each category.
## How to fix
Since the navigation can only display top-level sections, I propose splitting the navigation as follows:
- Marketing
- Community
- Brand
- Rituals
- Slack channels
Navigating to each of these sections will then display a content table for each, labeled "In this section" (as currently exists).
To do this, I made the following changes:
- Changed heading hierarchy throughout page
- added styling to h3 to include border-top
## Caveat
Since h2 is used to define the three categories on this page (Marketing, Community, Brand), h3 tag is now utilized to define sub-sections for each of the main categories. However, this styling is specific to the Marketing page of the handbook, and should not be applied to the other pages – which I do not know how to achieve.
* add page title to purpose, add marketing page-specific styles
Co-authored-by: Eric <eashaw@sailsjs.com>
* Handbook: Marketing page edits
* Marketing pass first iteration
* Handbook: adding community support to engineering
1st iteration
* Handbook:removing community support from marketing
1st iteration
* Handbook: new section for community support
* Handbook: Marketing second pass
Added sections with section links per team.
Ask @chris-mcgillicuddy if he wants to remove the style guide sections and editing sections on this page
Updating digital experience to brand - ask @eashaw for help with link redirects
TODO: Charlie: need to check the handbook links before merging.
* Consolidating style guide
Several sections of the handbook have their own styles guides with redundant content. I'm consolidating that content into one central location.
* Update README.md
* Update README.md
* Update README.md
* Merging Quality section with Engineering
I merged content from the Quality section of the handbook with Engineering. I added the ritual and slack channel DRIs from Quality to the Engineering tables.
* Delete README.md
* Creating Marketing division of the handbook
Marketing is comprised of Community, Digital Experience, Growth, and Handbook.
* Update marketing.md
* Update and rename handbook/company/marketing.md to handbook/marketing/README.md
* Update README.md
* Rename handbook/growth/README.md to handbook/marketing/growth.md
* Rename handbook/digital-experience/README.md to handbook/marketing/digital-experience.md
* Rename handbook/digital-experience/article-formatting-guide.md to handbook/marketing/article-formatting-guide.md
* Rename handbook/digital-experience/commonly-used-terms.md to handbook/marketing/commonly-used-terms.md
* Rename handbook/digital-experience/how-to-submit-and-publish-an-article.md to handbook/marketing/how-to-submit-and-publish-an-article.md
* Rename handbook/digital-experience/markdown-guide.md to handbook/marketing/markdown-guide.md
* Rename handbook/community/README.md to handbook/marketing/community.md
* Update markdown-guide.md
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
* Rename People to BizOps in handbook.
* Update README.md
* Update README.md
* Rename handbook/people/README.md to handbook/business-operations/README.md
* Rename handbook/people/ceo-handbook.md to handbook/business-operations/ceo-handbook.md
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
- Changed the "Use workflow from" instructions per advice from @zwinnerman-fleetdm
- Added note that "main" is not a valid image name and the commit hash must be used instead.
* update helper to use the osquery schema from the osquery/osquery-site repo
* update script description and generated json filename
* Add ritual to digital experience handbook
* add merged schema
* Update README.md
* Update get-extended-osquery-schema.js
* update to article submission guide
I made the following changes:
- I updated the guide to make it clear that submitting drafts as a Google Doc is the official article submission process.
- I did some housekeeping for improved clarity.
* Update handbook/digital-experience/how-to-submit-and-publish-an-article.md
* Create why-this-way.md
Moved "Why this way" to it's own page within Company handbook.
* Create development-groups.md
Added new page development-groups.md to Company handbook.
* Update README.md
Added space for Charlie to write summary for our new sections and add links to the nested pages.
* Update development-groups.md
Added meta tags to the page.
* Update why-this-way.md
* Update why-this-way.md
Changed head hierarchy to populate sub nav.
* preamble and links to sub pages
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
- Clean up the top section
- Clean up queries section
- Update naming for the sub-sections in the "Organization settings" section
- Remove `single-file-configuration.yml` and files under `multi-file-configuration/`
- Remove testing section from product handbook
updated Q3 OKR doc, we'll need to add Q4 at end of the month and probably set a process on who is responsible for updating the handbook to reflect the latest quarter
* Handbook: adding contact information for customers
I added information for free and paying customers to contact Fleet for support.
* Update README.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update and rename executive-assistant.md to ceo-handbook.md
- Renamed executive-assistant.md to ceo-handbook.md
- migrated CEO and EA-specific tasks
* Update README.md
- migrated CEO and EA-specific tasks to ceo-handbook.md
* Update README.md
- fixed a typo
* Update ceo-handbook.md
- fixed another typo
* Update meta tag on ceo-handbook.md
- fixed up meta tag on ceo-handbook.md
- Update "Learn how to use Fleet" docs page to walk a Fleet Sandbox user through adding their device and running a query
- Add a "Get operating system information" query to standard query library for the "Learn how to use Fleet" walkthrough
- Update Fleet's top level README to point users who want to try Fleet to Fleet Sandbox
- Update "How to install osquery..." (macOS, Windows, Linux) blog posts to point users who want to try Fleet to Fleet Sandbox
- Move `fleetctl preview` questions to "Contributing" FAQ section in docs. This is because `fleetctl preview` is now a testing tool for Fleet contributors
- Update "Deploying" docs to point users who want to try Fleet to Fleet Sandbox
* Codeowners: Reduce # of pings for reviews of docs
To avoid duplicative pings in Slack, reduce the number of folks who get automatically pinged about review requests when documentation, handbook, and website routes are changed.
I left Mike T and Chris both on the digital experience handbook so that PRs can be merged quickly there in many cases, regardless of timezone.
Also @chris-mcgillicuddy I made you responsible for either (a) approving and merging or (b) if there changes to meaning or code samples, requesting review from the on-call engineer.
* Update to reflect routing doc changes through Chris, and add sub-headings
* Pull the most relevant sentences to the top of each responsibility
* Use more peaceful language
* Adding a video to the Fleet docs
These instructions make sure embedded YouTube videos display correctly on mobile.
* Add files via upload
- uploaded video embed guide gif
* Update handbook/community/README.md
- added a gif to show how to find the YouTube video embed URL
* Updated image link in community/README.md
updated image link
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
* Update README.md
Added a ritual for lead pipeline review and a link to the overview video on YouTube.
* Update handbook/sales/README.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
This page is linked to from hiring materials, which don't always make the "open source is forever" point. This adds a link to accomplish that, for folks who are really digging in.
README:
- fixed broken link for "how to submit and publish an article
How to submit and publish an article:
- added links to "Article formatting guide" and "Markdown guide"
Article formatting guide:
- added link to Markdown guide
* Markdown guide for the handbook
Markdown guide for the handbook.
* Update markdown-guide.md
* Update markdown-guide.md
* Update markdown-guide.md
* Update markdown-guide.md
* Update markdown-guide.md
* Update handbook/digital-experience/README.md
* Update handbook/digital-experience/markdown-guide.md
* Handbook - Re-ordered Digital Experience README.md
- I repositioned Markdown to be under Voice and tone.
@Desmi-Dizney, I think you are right. Including the Markdown section under the section for writers is better.
* Update markdown-guide.md
- actioned review comments (https://github.com/fleetdm/fleet/pull/6864#pullrequestreview-1053545929)
- reformatted the markdown guide.
- updated nested list examples to display inside a table
- removed a couple of link examples that don't currently render on the website
* Update README.md
- I removed the Markdown section. I'd prefer to link to this guide as and when it's needed.
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* add article submission process
- added process-for-submitting-and-publishing-articles.md
- renamed article-formatting-guide.md
- updated links on README.md
* add anchor links
- add anchor links
* formatting changes and link fixes
- Changed up some formatting and fixed a couple of broken anchor links.
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/digital-experience/process-for-submitting-and-publishing-articles.md
* Update process-for-submitting-and-publishing-articles.md
- changed the title meta tag to lowercase.
* title update
- updated the page title in response to https://github.com/fleetdm/fleet/pull/7021
- fixed up some internal links to related pages
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Updated testing.md
Updated the name of testing.md to testing-and-local-development.md based off https://github.com/fleetdm/fleet/issues/4706
* add redirect for /docs/contributing/testing
Co-authored-by: Eric <eashaw@sailsjs.com>
* DRI update for Slack channel
Deleted Eric from the DRI list for digital experience slack channel.
* Update handbook/digital-experience/README.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Renamed Brand to be Digital experience
@eashaw and I changed this to be titled Digital experience.
* Capitalized Digital Experience in handbook/digital-experience/README.md
* Capitalized Digital Experience in handbook/digital-experience/README.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Done as per @mikermcneil's request in Slack
mikermcneil
@Desmi Dizney
can you update this slack channel in the relevant handbook to reflect this? https://fleetdm.slack.com/archives/C03MMC90MNU/p1658798689913439
mikermcneil
has renamed the channel from "help-operations" to "help-operations-and-contract-reviews"
* Website: add support for excludePageFromSectionIndex meta tag in Markdown content
* revert articles and docs changes
* move handbook pages into subfolders, rename brand to digital experience, update links
* update page script, add pages in same section to generated index
* remove newline
* add redirect for renamed handbook page (/handbook/brand -> /handbook/digital-experience)
* handbook: update relative page links
* update comment
* Update basic-handbook.page.js
* Revert .sailsrc change
* Update basic-handbook.ejs
* Update basic-handbook.page.js
* Update basic-handbook.page.js
* Update security.md
I added an example of how second-level sections could be introduced (linked to).
* update links on security.md, remove related pages
* change top level files filenames to README.md
* remove handbookSection
* Update basic-handbook.page.js
* only include top level pages in handbook index
* update relative links
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
* Update sales.md
- I renamed the writing principles section. The previous version was a bit of a tongue-twister for me :)
- I broke the principles into subheadings to make the section more scalable. We may need to add more principles later.
* Update sales.md
- I added an intro to the section
* Article formatting guidelines
Created as per https://github.com/fleetdm/fleet/issues/6570
* Update handbook/brand.md
* Added custom CTA image examples for handbook
Added images for instructions about how to use the custom CTA for articles.
* Updated Article for formatting guide on brand.md
I made some markdown and formatting fixes with Des.
* update relative image links
* Update handbook/brand.md
added context for what the meta tags are for when writing articles.
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* Update handbook/brand.md
Added clearer instructions for where to create a new file for an article.
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
I removed the <br> tag from the Rituals table.
FYI @Desmi-Dizney, nice idea to try to break up these sentences, but <br> should be avoided, in part because they become unruly at different browser sizes and cause ugly gaps in paragraphs. In this case it was forcing a [widow](https://www.fonts.com/content/learning/fontology/level-2/text-typography/rags-widows-orphans).
* Updated OOO handoff process
# This is created as per:
- https://github.com/fleetdm/confidential/issues/1517
## @CharlotteChance's notes for reference:
Handbook in People
Rough draft:
- Communicate what the responsibilities are when performing a handoff
- Communicate when and how long (setting expectations)
- Communicate who they should go to if they need help satisfying those responsibilities
- If time does not allow for this (i.e. family emergency, dramatic illness), call in help from your manager for assistance in the handoff
# I made updates to the Taking time off section.
I'm requesting @chris-mcgillicuddy's review.
* Update handbook/people.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/people.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
Co-authored-by: Charlie Chance <100798688+CharlotteChance@users.noreply.github.com>
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Fixed bad links on brand.md
- Fixed up some bad links that were pointing to localhost.
* fixed broken links on brand.md
- Fixed a couple more bad links
* OKR - Changed docs markdown editing process
Tagging @mike-j-thomas for review.
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update handbook/brand.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Update community.md
* Update brand.md
* Update customers.md
* Update community.md
* Update brand.md
@mike-j-thomas, should Docs (REST API) be changed as well?
* Update brand.md
* Update handbook/community.md
* Update handbook/customers.md
* Update handbook/community.md
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
* Added "Writing for the Sales team"
Created as per: https://github.com/fleetdm/fleet/issues/6671
@alexmitchelliii, this can be moved wherever you like. Let me know if you need any more help.
@mikermcneil, does this count as 5 sentences? 😂
* Update sales.md
* Update handbook/sales.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update handbook/sales.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Added glossary (first draft)
@mike-j-thomas, This is my first crack at building a table. I think I got it right but I'm open to feedback.
* Update brand.md
- I moved the position of the glossary to the end of the "writing at Fleet" section.
* second look
I took a second look at this for capitalization.
It's ready for your eyes @mike-j-thomas.
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update handbook/brand.md
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Update brand.md
* Update handbook/brand.md
* Update handbook/brand.md
* Update brand.md
* Apply suggestions from code review
Commiting the latest @Desmi-Dizney suggestion
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Handbook: Fleet - who does what info
Clarity on DRI between Fleet and Formation (accounting firm)
* Update handbook/people.md
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com>
* Editor pass - Handbook: CEO shadow program
Editor pass for:
- https://github.com/fleetdm/fleet/pull/6177/files
* Hankbook: Shadow program clean up
Co-authored-by: Charlie Chance <100798688+CharlotteChance@users.noreply.github.com>
* Handbook editor pass - Community
This has been edited for copy.
* Update community.md
* Update community.md
Added brief explanation of "Canonical" links
Co-authored-by: Katheryn Satterlee <me@ksatter.com>
