Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Workshop starters

Choose the directory for the language selected on the workshop homepage, then work directly inside it. There is no copy step. Change into that directory, open the same folder in your editor (code . from inside it, or any other editor's open-folder command), and stay there for every command. Starters are intentionally minimal scaffolds. The application-owned Web Content Accessibility Guidelines (WCAG) catalog and scoped permission/snapshot-reader helpers may be present for later lessons, but their executable entrypoints do not wire a Copilot client, session, streaming flow, local tool, MCP server, or report until the corresponding step.

Language Prerequisite Change directory and verify
.NET .NET 10 SDK cd start-accessibility/dotnet && dotnet build
Node.js Node.js 22+ cd start-accessibility/nodejs && npm install && npm run build
Python Python 3.11+ cd start-accessibility/python && python -m pip install -r requirements.txt && python -m py_compile *.py
Go Go 1.24+ cd start-accessibility/go && go build -mod=readonly ./...
Rust Rust 1.94+ cd start-accessibility/rust && cargo check --locked
Java Java 17+ (Maven Wrapper included) cd start-accessibility/java && ./mvnw compile

Because you edit these files in place, your work shows up in git status. That is expected. Run git checkout -- . from the repository root to restore a clean starter. Go, Rust, and Java tracks require the GitHub Copilot CLI on PATH when you later run the application. SDK setup and API references are available in the official Copilot SDK repository and cookbook.

Stay in your starter directory for the whole workshop. Return to the interactive viewer from the workshop homepage; do not open lesson Markdown directly.