Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 106

Handbook: Fix broken link in why-this-way.md (#20259)

Browse source 
Changes:
- Fixed a broken link on the why this way handbook page.
This commit is contained in:
Eric 2024-07-09 12:37:21 -05:00 committed by GitHub
parent ec11e3d1d0
commit 4ff20de14d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/company/why-this-way.md
View file

@ -48,7 +48,7 @@ There are three reasons for visiting [the docs](https://fleetdm.com/docs):
- **Committed learning**: "I've decided to learn this. I need a curriculum to get me there; with content that makes it as easy as possible, surface-level as possible. I want to learn how Fleet works and how to do all the things."
- **Quick reference**: "Is this thing broken or am I using it right? How do I use this?" Whether they just stumbled in from a search engine, an on-site search, or through the Fleet website navigation, visitors interested in quick reference are interested in getting to the correct answer quickly. Quick referencers search for REST API pages, the config surface of the Fleet server, agent options, how to build YAML for `fleetctl apply`, the built-in MDM profiles, the table schema, the built-in queries, reference architectures and cost calculators for deploying your own Fleet instance.
> Currently, Fleet only adds new "Quick reference" content to the [docs](fleetdm.com/docs). New "Committed learning" docs should be written as [articles](https://fleetdm.com/articles). Why? The docs surface area is large and Fleet iterates on features more quickly than we can update extensive how-tos. We've learned that users are more forgiving when articles are out-of-date. But, reference documentation always needs to be correct.
> Currently, Fleet only adds new "Quick reference" content to the [docs](https://fleetdm.com/docs). New "Committed learning" docs should be written as [articles](https://fleetdm.com/articles). Why? The docs surface area is large and Fleet iterates on features more quickly than we can update extensive how-tos. We've learned that users are more forgiving when articles are out-of-date. But, reference documentation always needs to be correct.
Everyone [can contribute](https://fleetdm.com/handbook/company#openness) to Fleet's documentation. Here are a few principles to keep in mind: