* 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
* Add notes re: OUI and wireshark OUI lookup for arp_cache
* More info on ARP spoofing
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
* Fix links in markdown
Co-authored-by: Eric <eashaw@sailsjs.com>
Co-authored-by: Guillaume Ross <guillaume@fleetdm.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
- Rename "Osquery logs" page to "Log destinations"
- Use exact product names in the log destination docs
- Move anchor links to the top of the page so that fleetdm.com/docs/log-destinations renders a sidebar
* 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>
Related to https://github.com/fleetdm/fleet/issues/8010 and https://github.com/fleetdm/fleet/issues/8013 this prevents a bug that happens when:
1. A team doesn't have a `config.features` key in the JSON stored in the table or `config` is `NULL`
2. The team is edited from the UI
All `config.features` will default to `false`, which can be a problem if your global settings are `true` for both (which is the default)
* Create zero-trust-attestation-with-fleet
* Added images
I made the following changes:
- added .md file extension
- added artwork for the article
* Image update
- updated thumbnail image
- moved position of zero touch diagram
* Added file extension
* Added revisions from Google doc
Incorporated revisions I had been discussing with Mo.
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* create new components for query side panel
* add reusable icon component that uses svg for icons
* integrate with new osquery_fleet_schema.json data
* update UI to work with osquery_fleet_schema.json
* add remark-gfm to safely support direct urls in markdown
* move fleet ace into markdown component so we can render code with ace editor
* add testing for new query sidebar
* remove incomplete tests for query sidepanel