Summary
docs/BOARD_STATUS.md renders the full per-platform CI badge matrix inline, which makes the page very long to scroll through before reaching anything else. Wrap the platform build matrix inside a <details> block so readers can expand it on demand rather than having it dominate the page by default.
Proposal
Wrap the "Per-platform CI badges" section (and/or each platform-family subsection) in GitHub-flavored <details> / <summary> so the matrix is collapsed by default:
<details>
<summary>Per-platform CI badges</summary>
### AVR
[]
...
</details>
Options worth considering:
- One outer
<details> around the entire matrix (simplest).
- A
<details> per family (AVR, ESP32, Teensy, STM32, CH32V, ...) so readers can expand only the platform they care about.
Affected files
docs/BOARD_STATUS.md — primary location of the matrix
- Any other doc that embeds the same badge list (search for
actions/workflows/build- references)
Acceptance criteria
Summary
docs/BOARD_STATUS.mdrenders the full per-platform CI badge matrix inline, which makes the page very long to scroll through before reaching anything else. Wrap the platform build matrix inside a<details>block so readers can expand it on demand rather than having it dominate the page by default.Proposal
Wrap the "Per-platform CI badges" section (and/or each platform-family subsection) in GitHub-flavored
<details>/<summary>so the matrix is collapsed by default:Options worth considering:
<details>around the entire matrix (simplest).<details>per family (AVR, ESP32, Teensy, STM32, CH32V, ...) so readers can expand only the platform they care about.Affected files
docs/BOARD_STATUS.md— primary location of the matrixactions/workflows/build-references)Acceptance criteria
<details>group by default#esp32) still resolve if we go with per-family groups