Slide 17
Issue Template System
Explain issue template strategy and structured intake.
Source markdown
This page is generated from the canonical slide file in the repository and the supporting references listed below.
Key points
- Template catalogue supports different work types.
- Configured templates improve required metadata quality.
- Structured intake reduces back-and-forth and speeds assignment.
Speaker notes
- Acknowledge trade-off: too many templates can overwhelm contributors.
- Explain active curation and simplification strategy.
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.
References
`.github/ISSUE_TEMPLATE/config.yml` Reference used in this slide `.github/ISSUE_TEMPLATE/README.md` Reference used in this slide `.github/ISSUE_TEMPLATE/23-ai-ops.md` Reference used in this slide `.github/ISSUE_TEMPLATE/03-feature.md` Reference used in this slide `.github/ISSUE_TEMPLATE/02-bug.md` Reference used in this slide