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
