Slide 02
Why a .github Control Plane
Explain why centralising standards in one .github repo was the first successful step.
Source markdown
This page is generated from the canonical slide file in the repository and the supporting references listed below.
Key points
- Shared community health and governance conventions.
- Canonical labels, issue types, and template strategy.
- Reusable workflows and instruction standards.
Speaker notes
- Emphasise this was a practical response to repeated delivery friction.
- Mention the control-plane mental model: one source of truth, many consuming repos.
Accessibility notes
- Keep layout simple: title + 3 bullets + one visual zone.
- Use minimal visuals (one icon, one screenshot, or one simple diagram only).
- Avoid dense process diagrams, nested callouts, and complex animation.
- Keep on-slide text short (roughly 25-40 words total where possible).
- Use high contrast and consistent spacing; prioritise readability over decoration.