Alex: Welcome back. Today we're making the workshop materials easier to reach, easier to save, and easier to come back to when you need them.

Jamie: I like this topic because it sounds simple until you're actually trying to find the right file five minutes before an exercise starts.

Alex: Exactly. The same content can show up as Markdown source files, HTML pages, a live website, a local folder on your computer, and even this podcast series. Each format has a different job in your workflow.

Jamie: So there isn't one perfect way to read the workshop. There are a few good doors into the same material.

Alex: Yes. The main course repository is Community-Access/git-going-with-github, and this appendix supports the pre-workshop setup chapter. If a facilitator gives you a workshop link or a Learning Room link, use that shared link first, then use the repository when you want to browse, download, or update the full set of materials.

---

Jamie: If I'm online and just want to read, where should I start?

Alex: Start with the HTML site at community-access.org when your facilitator points you there. In some workshop setups, the site may also be shared as a GitHub Pages URL that looks like organization dot github dot io slash Learning-Room. The landing page is usually index.html, and it acts like the workshop homepage.

Jamie: What makes that better than opening random files on GitHub?

Alex: The HTML version is built for reading. Internal links between chapters and appendices work like a website, and the pages include headings, skip-to-content links, breadcrumb navigation, and ARIA landmarks. With NVDA or JAWS, you can use H to move by heading, and you can use D in NVDA or R in JAWS to jump to the main landmark on a page.

Jamie: And for low vision learners, the browser is often the familiar place to control zoom, contrast, and spacing.

Alex: Right. The HTML pages are a good workshop default because they need almost no setup. Bookmark the URL so you can get back quickly, especially during live instruction when the group is moving from one chapter to another.

---

Alex: You can also read the files directly on GitHub.com without downloading anything.

Jamie: This is the part where I always wonder, am I supposed to click the README, the docs folder, or some tiny file name?

Alex: On the repository page, the README renders automatically and works like a front page. To read chapters and appendices, open the docs folder, then choose a file ending in .md. GitHub renders Markdown as formatted text, so you get headings, links, and code blocks instead of only raw punctuation.

Jamie: GitHub's file list can feel crowded with a screen reader. What are the useful shortcuts?

Alex: On the main repository page, press T to open the file finder, then type part of a file name to jump straight to it. In the file listing, treat it like a table or grid and move through rows with your screen reader's table navigation or arrow keys. Once you're inside a file, use H to move by heading, and use the breadcrumb links near the top to move back up through the path, such as repository, docs, then the file name.

Jamie: And the Raw button is for when you want the actual file content, not GitHub's pretty view?

Alex: Yes. The rendered view is better for reading. Raw is useful when you want to save the exact file, because the browser shows the plain source and you can save it from there.

---

Jamie: What if I want everything on my computer before the workshop, not just one page at a time?

Alex: If you have Git installed, cloning is the recommended route because it gives you a full copy that can be updated later. The command is git clone https://github.com/community-access/git-going-with-github.git. Then move into the folder that was created by the clone, usually with cd git-going-with-github; if your facilitator gave you a different repository such as a Learning Room, use that folder name instead.

Jamie: So cloning brings down more than just the chapters.

Alex: It brings the Markdown source, the HTML output, scripts, learning-room materials, templates, and project files. After cloning, you can open the folder in VS Code with code dot, then use the Explorer panel with Ctrl+Shift+E to browse the file tree. Arrow to a file and press Enter to open it.

Jamie: And if someone does not have Git installed or just does not want the command line?

Alex: Use Download ZIP from GitHub.com. Go to the repository page, find the green Code button near the top of the file listing, open the dropdown, choose Download ZIP, save the file, and extract it to a folder on your computer.

Jamie: That Code button can be a little slippery with a screen reader.

Alex: It is usually after the branch selector and near the repository description. In NVDA or JAWS browse mode, press B to move by buttons until you hear Code, then activate it with Enter or Space. Arrow through the menu until you find Download ZIP. Just remember that a ZIP is a snapshot; it will not update itself later.

---

Alex: Sometimes you only need one file, like one appendix, one chapter, or a screen reader cheat sheet.

Jamie: Please tell me I don't have to download the whole repository for that.

Alex: You don't. On GitHub.com, navigate to the file you want, then use the Raw button above the file content. When the raw file opens in the browser, press Ctrl+S on Windows or Linux, or Cmd+S on macOS, and save it where you want it.

Jamie: Does that work for the HTML files too?

Alex: Yes. Go into the html folder, open the .html file you want, choose Raw, and save it the same way. If you already cloned the repository, the file is already on your machine, so you can just copy it from the local folder.

Jamie: Before we go farther, what am I actually looking at inside the repository?

Alex: The docs folder has the Markdown source for the chapters and appendices. The html folder has pre-built web page versions, including html/docs for the chapter and appendix pages. The learning-room folder holds practice repository files such as challenges, group exercises, and setup guides, with matching HTML versions under html/learning-room.

Jamie: And the other folders are more project infrastructure?

Alex: Right. The .github folder contains issue templates, a pull request template, Copilot agents, and slash commands. The scripts folder contains the build script that converts Markdown to HTML. At the root of the repository, you will find the README, agendas, facilitator guide, contributing guide, and other project files.

---

Jamie: Let's say I downloaded the materials before traveling. Can I read everything without internet?

Alex: Yes. Markdown files open in any text editor because they are plain text with lightweight formatting. In VS Code, open a .md file and press Ctrl+Shift+V to open the Markdown preview, which renders headings, links, and code blocks in a more readable view.

Jamie: That preview is helpful for low vision users too, especially if VS Code is already set up with a preferred theme.

Alex: Exactly. VS Code's preview follows your editor environment, including high-contrast themes. For the most polished offline reading, open html/index.html in your browser and navigate from there; the local HTML pages support browser zoom and still link to each other.

Jamie: Do the accessibility features survive when the HTML files are local?

Alex: They do. The landmarks, heading structure, and skip links are embedded in the files, so the offline version behaves much like the online version. The links at the bottom of pages also help you move to nearby chapters and appendices without hunting through folders.

Jamie: So the simple recommendation is browser for reading, VS Code when I want to inspect or edit.

Alex: That's a solid split. Open html/index.html when you want a local homepage. Open the repository folder in VS Code when you want to browse files, read Markdown, or prepare an edit.

---

Alex: Materials change, so it helps to know how your copy gets updated.

Jamie: This is where cloning and ZIP downloads really behave differently.

Alex: They do. If you cloned with Git, open a terminal in your local copy, move into the repository folder, and run git pull. If you have not changed local files, Git usually updates cleanly. If you have local edits, Git may try to merge them, and the merge conflicts chapter is the place to go if files collide.

Jamie: And what about the HTML after pulling changes?

Alex: If you're maintaining a local HTML copy from the source, run npm run build:html after pulling so the generated pages match the latest Markdown. If you downloaded a ZIP, there is no one-command update. Download a fresh ZIP from the repository and replace your old folder.

---

Jamie: When would you choose each format?

Alex: For live workshop reading, use the online HTML site because it is current, accessible, and does not require setup. For a quick lookup, GitHub.com is convenient. For offline reference, use the local HTML folder. For contributing improvements, edit the Markdown files in docs. For archiving a copy, use a ZIP or a clone. For staying updated over time, clone is the best choice because git pull is repeatable.

Jamie: And this audio series is another format too, right?

Alex: Yes. The podcast is useful before reading if you want a preview, and after reading if you want reinforcement. It is also a good alternative when visual reading is tiring or when you want to review concepts away from the screen.

Jamie: What about printing or exporting? Some people still like a reference packet.

Alex: For printing, the HTML version is usually easiest: open the page in a browser and use print or save as PDF. For Markdown, use the VS Code preview and print from there, or copy the content into a tool that formats it the way you need. If accessibility matters for the exported file, check the result with your screen reader or magnification setup before depending on it.

Jamie: And if something looks different later because GitHub changed its interface?

Alex: Use the course repository and the facilitator's shared site as the source of truth for workshop content. For GitHub platform behavior, check GitHub's official documentation and changelog because buttons, menus, and shortcuts can change over time.

Jamie: So the big choice is not mysterious: online HTML for the live workshop, local HTML for offline reading, Markdown for editing, Git clone for updates, ZIP for a simple snapshot, and audio when listening is the better path.

Alex: Exactly. Pick the format that lets you stay oriented, keep moving, and return to the material when you need it.