-
Notifications
You must be signed in to change notification settings - Fork 6
appendix y accessing workshop materials
Listen to Episode 42: Accessing Workshop Materials - a conversational audio overview of this chapter. Listen before reading to preview the concepts, or after to reinforce what you learned.
Why this appendix exists: The workshop content is available in multiple formats - Markdown source files, pre-built HTML pages, and a live GitHub Pages site. This guide explains how to access each format, download materials for offline use, and keep your copy up to date.
- Browsing Online (GitHub Pages)
- Reading on GitHub.com
- Downloading Everything
- Downloading Individual Files
- What's in Each Folder
- Offline Reading
- Keeping Your Copy Updated
- Which Format Should I Use?
If the facilitator has enabled GitHub Pages for this repository, the workshop materials are available as a website at a URL like:
https://<organization>.github.io/Learning-Room/
Your facilitator will share the exact URL. Once you have it:
- Open the URL in your browser
- The landing page (
index.html) is the workshop homepage - equivalent to the README - Use headings (
Hkey in NVDA/JAWS browse mode) to navigate within any page - All internal links between chapters and appendices work - click any cross-reference to go directly to that page
- Bookmark the URL for quick access during the workshop
Screen reader tip: The HTML pages include skip-to-content links, breadcrumb navigation, and ARIA landmarks. Press D (NVDA) or R (JAWS) to jump to the main landmark on any page.
For details on how GitHub Pages works, see Appendix P - Publishing with GitHub Pages.
You can read every file directly on GitHub.com without downloading anything:
- Go to the repository page (your facilitator will share the link)
- The README renders automatically as the repository homepage
- Click into the
docs/folder to see all chapters and appendices - Click any
.mdfile - GitHub renders it as formatted text with headings, links, and code blocks
-
File list: The repository file listing is a grid. Use
Tto jump to the file table, then arrow keys to navigate rows -
File content: Once inside a file, GitHub renders the Markdown. Use
Hto navigate headings -
Breadcrumbs: At the top of each file view, breadcrumb links show the path (e.g.,
Learning-Room / docs / 06-working-with-pull-requests.md). Use these to navigate back -
Go to File shortcut: Press
Ton the repository's main page to open the file finder - type any filename to jump to it
Cloning gives you a full copy of the repository that you can update later with git pull:
# Clone the repository
git clone https://github.com/community-access/Learning-Room.git
# Move into the folder
cd Learning-RoomAfter cloning, every file (Markdown source, HTML output, scripts, learning-room materials) is on your computer.
Screen reader tip: After cloning, open the folder in VS Code (code .) and use the Explorer panel (Ctrl+Shift+E) to browse the file tree. Press Enter on any file to open it in the editor.
If you do not have Git installed or prefer not to use the command line:
- Go to the repository page on GitHub.com
- Press
Tto find the file finder, or navigate to the green Code button (it is a dropdown button near the top of the file listing) - Activate the Code button - a dropdown menu opens
- Choose Download ZIP
- Save the file and extract it to a folder on your computer
- The Code button is near the repository description, after the branch selector
- In NVDA/JAWS browse mode, press
Bto jump between buttons until you reach "Code" - Activate it with
EnterorSpace - The dropdown contains options including "Download ZIP" - arrow down to find it
Note: A ZIP download is a snapshot. It does not update automatically - see Section 7 for how to get updates.
To download a single file (for example, one chapter or the screen reader cheat sheet):
- Navigate to the file in the repository
- Click the Raw button (it appears above the file content, in the toolbar with "Preview", "Code", "Blame" buttons)
- The browser shows the raw file content
- Press
Ctrl+S(Windows/Linux) orCmd+S(macOS) to save the page
For HTML files: Navigate to the html/ folder and download the .html version of any file using the same Raw → Save method.
If you have already cloned the repo, every file is already on your computer. Open the folder and copy whichever files you need.
| Folder | Contents | Format |
|---|---|---|
docs/ |
All 17 chapters (00-16) and 31 appendices (A-Z, AA-AE) | Markdown (.md) |
html/ |
Pre-built HTML versions of every Markdown file | HTML (.html) |
html/docs/ |
HTML versions of all chapters and appendices | HTML (.html) |
learning-room/ |
Practice repository files: challenges, group exercises, setup guides | Markdown (.md) |
html/learning-room/ |
HTML versions of learning-room documents | HTML (.html) |
.github/ |
Issue templates, PR template, Copilot agents, slash commands | YAML and Markdown |
scripts/ |
Build script that converts Markdown to HTML | JavaScript |
Root (/) |
README, agendas, facilitator guide, contributing guide, and other project files | Markdown (.md) |
Once you have downloaded or cloned the repository, you can read everything offline:
Open .md files in any text editor. They are plain text with lightweight formatting syntax. VS Code renders Markdown with a preview panel (Ctrl+Shift+V).
- Open
html/index.htmlin any web browser - All internal links between pages work locally - no internet connection required
- Navigate between chapters using the links at the bottom of each page
Screen reader tip: The HTML files work the same offline as online. All ARIA landmarks, heading structure, and skip links are embedded in each file.
-
VS Code with Markdown: Open the repo folder in VS Code, browse the Explorer, and read files directly in the editor. Use
Ctrl+Shift+Vto open the rendered preview -
Browser with HTML: Open
html/index.htmland navigate from there - this gives the most polished reading experience
# Navigate to your local copy
cd Learning-Room
# Pull the latest changes
git pullIf you have not made local changes, this updates your copy cleanly. If you have local edits, Git will attempt to merge - see Chapter 7 - Merge Conflicts if needed.
After pulling, rebuild the HTML to ensure it matches:
npm run build:htmlDownload a fresh ZIP from the repository and replace your local copy. There is no incremental update for ZIP downloads.
| Need | Best format | Why |
|---|---|---|
| Reading during the workshop | GitHub Pages (online HTML) | No setup, always current, fully accessible |
| Offline reference |
Local HTML (html/ folder) |
Works in any browser, no internet needed, styled and navigable |
| Editing or contributing |
Markdown (.md files) |
The source format - edit these, then rebuild HTML |
| Quick lookup of one section | GitHub.com | Navigate directly in the browser, no download |
| Archiving a copy | ZIP download or Git clone | Full snapshot of all materials |
| Staying updated long-term | Git clone | One-command updates with git pull
|
Return to: Appendix X - Copilot AI Models | Appendix A - Glossary | README