Awesome GitHub Conference site on GitHub Pages
WCEU 2026
Site
WCEU 2026 talk

Governing AI-assisted workflows with a .github control plane

This page collects the public-facing summary for the conference talk and the slide source tree that supports it. The story is practical: keep standards in one place, make them reusable, and let the repo do the operational work.

Open slide source Browse all slides View references
Talk focus
Governance model Why fragmented governance and automation slow teams down.
Control plane How .github becomes the canonical home for shared standards.
Outcomes What changes when the repo, workflows, and docs move together.
20 slide pages Every slide in the conference deck now has its own public subpage and source link.

Talk outline

Open with the pressure

Start with the operational pain: many repositories, drifting standards, and too much delivery friction.

Show the architecture

Explain how governance files, reusable workflows, and instruction packs fit together without turning the repo into a document dump.

Close with measurable change

Tie the system back to outcomes, accountability, and the maintenance costs it avoids over time.

Slide index

Each slide now has a public subpage with the summary, references, and a link back to the talk page.

Open index
Slide 01

Hook and Stakes

Open with the operational pain and why this matters now.

Open slide page
Slide 02

Why a .github Control Plane

Explain why centralising standards in one .github repo was the first successful step.

Open slide page
Slide 03

Inheritance Boundaries

Clarify what central .github can and cannot enforce by default.

Open slide page
Slide 04

Control Plane Architecture

Visualise the architecture of governance data, workflows, and standards.

Open slide page
Slide 05

Canonical Governance Assets

Show the concrete governance assets that made scaling possible.

Open slide page
Slide 06

Why We Pivoted

Explain why centralisation alone was insufficient and why a plugin model emerged.

Open slide page

Accessibility guidance

The wider wceu-2026 pack consistently points to the same public-facing advice:

  • Use high contrast and consistent spacing; prioritise readability over decoration.
  • Avoid relying on colour alone and keep the visual language simple enough for quick scanning.
  • Use keyboard-friendly navigation, predictable page structures, and minimal motion.
  • Keep speaker notes and live venue checks as part of the delivery plan.
  • Treat diagrams, charts, and link labels as accessibility work, not decoration.

The slide notes and audit material in wceu-2026/ACCESSIBILITY_AUDIT.md, wceu-2026/VISUAL_DESIGN_SPECIFICATIONS.md, and wceu-2026/FINAL_REVIEW_CHECKLIST.md back up that guidance.