Skip to content

Add the accessibility statement, Discussions and the barrier form link - #71

Merged
stphnwlsh merged 2 commits into
mainfrom
feature/accessibility-and-governance
Nov 18, 2026
Merged

stphnwlsh merged 2 commits into
mainfrom
feature/accessibility-and-governance

Conversation

@stphnwlsh

@stphnwlsh stphnwlsh commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Summary

Brings this template up to the rest of the community standards. It adds ACCESSIBILITY.md (GitHub doesn't hand it down from .github), puts the accessibility barrier form and Discussions into config.yml, copied from the pool, and adds both to SUPPORT.md and the README. CONTRIBUTING.md gets a short accessibility note, says contributions come in under MIT with no CLA, and links governance. The docs-and-voice skill gets accessibility rules, and releases gets the monthly numbers step.

The options tables now put each option's long and short form on separate lines (--name, then -n), so a narrow screen can't split the pair down the middle. That covers the README and the template-authoring skill, and docs-and-voice now says to do it. NuGet doesn't render HTML, so NUGET.md gives the short form its own column instead.

It's the same change in all five templates, so Shared Layers Drift stays quiet. It depends on LeanMeanCleanApps/.github#120 for the pool and the form, and on the site PRs for the statement page, so merge those first. Nothing here is packed into the template.

Related issues

Part of LeanMeanCleanApps/.github#114

Type of change

  • Bug fix
  • New feature
  • Breaking change (the generated solution or template parameters change in a way existing users will notice)
  • Refactoring or clean-up
  • Documentation
  • Build, pipeline or dependency update

Shared layers

  • This only touches the Presentation layer of this template.
  • This touches the Application or Infrastructure layers, tests, pipeline or repository setup, so it needs to be carried across all five templates.

Checklist

  • dotnet build and dotnet test pass locally with no warnings. No code changed, so CI is doing the honours.
  • I added or updated tests, and line coverage stays at or above 95%.
  • I updated the README or docs where behaviour changed.
  • If this changes how we do something, I updated the matching skill in .agents/skills.
  • I checked the template still installs and creates a working solution (see CONTRIBUTING.md).

@github-actions github-actions Bot added enhancement New feature or request build labels Nov 18, 2026
@stphnwlsh stphnwlsh self-assigned this Nov 18, 2026
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Build Pipeline

✅ Ready to merge. Every stage passed.

Stage Result Details
Build 🟢 Passed Version 2026.11.18.237-pr-71 · Template package 234 KB
Test 🟢 Passed 236 passed · 0 failed · 0 skipped · Template installs, builds and passes its tests
Coverage 🟢 Passed 100% (760 of 760 lines) · Needs 95%
Static Analysis 🟢 Passed No open CodeQL alerts
Dependency Review 🟢 Passed 0 vulnerable packages · 0 licence problems
Container Scan 🟢 Passed Image starts and answers · No open Trivy alerts

Commit 5f2ab0d · Full run

@stphnwlsh
stphnwlsh merged commit 05394c4 into main Nov 18, 2026
13 checks passed
@stphnwlsh
stphnwlsh deleted the feature/accessibility-and-governance branch November 18, 2026 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant