fleet/docs/Contributing
Rachael Shaw 86b80e28ed
Documentation v4.76.0 (#34943)
Documentation changes for the 4.76 release
2025-11-11 09:30:14 -05:00
..
adr ADR-0006: Replace no team with default team (#32883) 2025-09-16 12:54:21 -05:00
architecture Fix duplicate note and while we're at it some typos under docs/ (#32575) 2025-09-09 19:33:18 -03:00
assets SCIM Entra ID support (#28832) 2025-05-08 13:02:49 -05:00
getting-started Update host foreign vitals IdP guide + related tweaks (#35229) 2025-11-05 13:55:49 -06:00
guides Initial support for in-house apps on iOS/iPadOS (#34802) 2025-10-28 08:33:58 -04:00
product-groups Ingest, store, consider in unique_identifier, and serve upgrade_codes for Windows software (#34786) 2025-11-07 15:33:31 -08:00
reference Documentation v4.76.0 (#34943) 2025-11-11 09:30:14 -05:00
research Instructions to create a public mTLS reverse proxy (#33906) 2025-10-08 14:46:33 -05:00
responsibilities Organize contributor docs and establish ADR process and template (#29101) 2025-05-17 15:03:52 -05:00
rituals Update sprint retrospective guidelines with tool recommendations (#34543) 2025-10-20 15:22:43 -05:00
workflows Update release workflow documentation with tag examples (#35290) 2025-11-10 13:14:56 -06:00
README.md Update contrib docs headers to sentence case (#29276) 2025-05-20 11:26:35 -05:00

Fleet Contributor Documentation

Welcome to the Fleet contributor documentation! This documentation is designed to help you contribute to the Fleet project.

Documentation structure

The documentation is organized into the following sections:

Product groups

Fleet is organized into three main product groups:

  • MDM - Mobile Device Management
  • Orchestration - Device orchestration using osquery
  • Software - Software inventory, vulnerability management, and software installation

Contributing

If you're new to Fleet, we recommend starting with the Getting Started section to set up your development environment.

Once you're set up, you can explore the Guides section to learn how to contribute to specific areas of the project.

Architectural Decision Records (ADRs)

We use Architectural Decision Records to document significant architectural decisions. If you're making a significant architectural change, please create an ADR to document your decision.