* 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>
