3b471e74b7
Adds onboarding decision tree to getting-started/README.md so users can quickly identify the right setup command for their situation. Adds hardware vision overview to hardware/README.md explaining the Peripheral trait and supported board types. Expands project/README.md with scope explanation describing the purpose of project snapshots and how they relate to documentation maintenance. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
17 lines
602 B
Markdown
17 lines
602 B
Markdown
# Project Snapshot & Triage Docs
|
|
|
|
Time-bound project status snapshots for planning documentation and operations work.
|
|
|
|
## Current Snapshot
|
|
|
|
- [../project-triage-snapshot-2026-02-18.md](../project-triage-snapshot-2026-02-18.md)
|
|
|
|
## Scope
|
|
|
|
Project snapshots are time-bound assessments of open PRs, issues, and documentation health. Use these to:
|
|
|
|
- Identify documentation gaps driven by feature work
|
|
- Prioritize docs maintenance alongside code changes
|
|
- Track evolving PR/issue pressure over time
|
|
|
|
For stable documentation classification (not time-bound), use [docs-inventory.md](../docs-inventory.md).
|