Stage 3.8: rewrite stale /media/ep## audio refs in html/ tree

Author: GitHub Workshop Bot

html/admin/PODCASTS.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Pre-Workshop Setup</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep01-pre-workshop-setup.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-01-pre-workshop-setup.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep01-pre-workshop-setup.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-01-pre-workshop-setup.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep01-pre-workshop-setup.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-01-pre-workshop-setup.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome to Git Going with GitHub. Before the workshop really begins, this episode is about getting everything ready so Day 1 can start with learning, not troubleshooting.</p><p><strong>Jamie:</strong> And that matters a lot for this audience, right? Because setup is never just setup. It can include browser quirks, screen reader settings, account security, and a bunch of little choices that affect whether GitHub feels smooth or frustrating.</p><p><strong>Alex:</strong> Exactly. This is a Community Access workshop, and the core message is: please do this at least one day before the event. If something goes wrong, use the Community Access support repository and support discussions so help can happen before class time.</p><p><strong>Jamie:</strong> I also noticed a big theme here: tools change.</p></details>
     </article>

html/docs/00-pre-workshop-setup.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Choose Your Tools</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep44-choose-your-tools.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/agents-04-choose-your-tools.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep44-choose-your-tools.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/agents-04-choose-your-tools.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep44-choose-your-tools.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/agents-04-choose-your-tools.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Before anyone writes code or worries about commands, we need a map of the tools. This lesson is a guided tour of five different ways to work with GitHub: the website, a browser-based editor, a desktop editor, a desktop Git app, and the command line.</p><p><strong>Jamie:</strong> So the big idea is not, pick one forever. It&#39;s, learn the landscape so later instructions make sense.</p><p><strong>Alex:</strong> Exactly. And that matters because there is no single right way to use GitHub. Some people prefer the browser. Some want a visual desktop app. Some love a terminal. Many people switch tools depending on the task.</p><p><strong>Jamie:</strong> That feels especially important for accessibility. If one path works better with your screen reader or your low vision setup, that path is valid.</p></details>
     </article>

html/docs/01-choose-your-tools.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Understanding GitHub on the Web</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep02-github-web-structure.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-02-github-web-structure.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep02-github-web-structure.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-02-github-web-structure.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep02-github-web-structure.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-02-github-web-structure.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Before we do deeper GitHub work, we need a mental map. If GitHub has ever felt like a maze of tabs, sidebars, and pages that all blur together, this lesson is here to fix that.</p><p><strong>Jamie:</strong> And this is especially important for learners using screen readers, magnification, zoom, high contrast themes, or just anyone who wants a reliable way to know, where am I, and what kind of page is this?</p><p><strong>Alex:</strong> Exactly. And one quick administrative note before we begin: this lesson pairs with an audio episode and with two appendices, a glossary and a screen reader cheat sheet. It also points learners to GitHub&#39;s own docs and GitHub accessibility documentation as the authoritative references.</p><p><strong>Jamie:</strong> So this is not just theory. It&#39;s the orientation system for everything that comes next.</p></details>
     </article>

html/docs/02-understanding-github.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Navigating Repositories</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep03-navigating-repositories.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-03-navigating-repositories.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep03-navigating-repositories.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-03-navigating-repositories.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep03-navigating-repositories.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-03-navigating-repositories.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting comfortable inside GitHub repositories: how they&#39;re laid out, how to orient yourself quickly with a screen reader or keyboard, and how to move from, &quot;I found a repo,&quot; to, &quot;I actually know where things are.&quot;</p><p><strong>Jamie:</strong> And this is one of those chapters where the goal is not speed, right? It&#39;s confidence.</p><p><strong>Alex:</strong> Exactly. This is a foundation lesson. There are no challenge tasks here, no automation checks. The point is to build a reliable mental map before later chapters ask you to work with issues, pull requests, and traceable contributions.</p><p><strong>Jamie:</strong> So if someone&#39;s feeling pressure to perform already, this is a good place to exhale.</p></details>
     </article>

html/docs/03-navigating-repositories.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>The Learning Room</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep04-the-learning-room.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-04-the-learning-room.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep04-the-learning-room.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-04-the-learning-room.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep04-the-learning-room.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-04-the-learning-room.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re getting oriented to something you&#39;ll use constantly in the workshop: your Learning Room. Think of it as your personal practice repository on GitHub, built so you can learn the full workflow safely and realistically.</p><p><strong>Jamie:</strong> So this is not just a folder somewhere. It&#39;s an actual GitHub repository with issues, branches, pull requests, and automation?</p><p><strong>Alex:</strong> Exactly. When you accept the GitHub Classroom assignment, GitHub makes a private copy of the workshop template repository for you. That copy lives in the workshop organization and is named something like learning-room-your-username. You get write access to that repo. You can create branches there, open pull requests there, and receive automated feedback there.</p><p><strong>Jamie:</strong> And just to clear up a very common beginner question: am I supposed to work in the original template repository?</p></details>
     </article>

html/docs/04-the-learning-room.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Working with Issues</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep05-working-with-issues.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-05-working-with-issues.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep05-working-with-issues.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-05-working-with-issues.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep05-working-with-issues.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-05-working-with-issues.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re working with one of the most important parts of GitHub: issues.</p><p><strong>Jamie:</strong> And for a lot of learners, this is where GitHub starts to feel social, right? Not just files and commits, but conversation.</p><p><strong>Alex:</strong> Exactly. Issues are where people report bugs, request features, ask for clarification, track chores, and coordinate work. In open source, a lot of collaboration begins there.</p><p><strong>Alex:</strong> Before we get into the mechanics, a few support notes matter here. This chapter pairs well with the official GitHub documentation about issues, GitHub&#39;s accessibility guide for issues, and the GitHub Accessibility Lab CLI guide. There are also related appendices on advanced search, GitHub Mobile, and a screen reader cheat sheet.</p></details>
     </article>

html/docs/05-working-with-issues.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Working with Pull Requests</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep06-working-with-pull-requests.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-06-working-with-pull-requests.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep06-working-with-pull-requests.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-06-working-with-pull-requests.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep06-working-with-pull-requests.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-06-working-with-pull-requests.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. This time we&#39;re getting into pull requests, which is where individual edits turn into shared contributions.</p><p><strong>Jamie:</strong> So this is the moment where work stops being just &quot;my change&quot; and starts becoming something the project can actually review and merge.</p><p><strong>Alex:</strong> Exactly. And for blind and low-vision contributors, pull requests are also where navigation strategy matters a lot: headings, landmarks, tab choices, diff reading, comment forms, and status checks.</p><p><strong>Jamie:</strong> And this lesson is specifically about doing that accessibly, with a screen reader, keyboard-first, and with some CLI support too.</p></details>
     </article>

html/docs/06-working-with-pull-requests.html

@@ -214,13 +214,13 @@ <h2 class="companion-title">Companion Podcast and Transcript</h2>
     <article class="companion-card">
       <h3>Merge Conflicts Are Not Scary</h3>
       <p class="companion-note">Companion audio: this episode reinforces key ideas and may not be a word-for-word reading of this page.</p>
-      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ep07-merge-conflicts.mp3">
+      <audio controls preload="none" class="companion-player" src="https://lp.csedesigns.com/ggg/media/ch-07-merge-conflicts.mp3">
         Your browser does not support the audio element.
       </audio>
       <p class="companion-links">
-        <a href="https://lp.csedesigns.com/ggg/media/ep07-merge-conflicts.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
+        <a href="https://lp.csedesigns.com/ggg/media/ch-07-merge-conflicts.mp3" target="_blank" rel="noopener noreferrer">Open audio file (external)</a>
         <span aria-hidden="true"> · </span>
-        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ep07-merge-conflicts.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
+        <a href="https://github.com/Community-Access/git-going-with-github/blob/main/podcasts/scripts/chapters/ch-07-merge-conflicts.txt" target="_blank" rel="noopener noreferrer">Full transcript source (external)</a>
       </p>
       <details class="companion-preview"><summary>Transcript preview</summary><p><strong>Alex:</strong> Welcome back. Today we&#39;re talking about merge conflicts, and I want to start by lowering the temperature right away. Merge conflicts are normal. They are not proof that you broke Git, and they are not a sign that you are bad at collaboration.</p><p><strong>Jamie:</strong> That helps, because the phrase merge conflict sounds dramatic.</p><p><strong>Alex:</strong> It does. But in practice, a merge conflict just means Git found two overlapping changes and needs a human decision. This lesson is about understanding what that means, how to prevent conflicts when you can, and how to resolve them calmly when they show up.</p><p><strong>Alex:</strong> A quick orientation before we dig in. This chapter pairs well with a short companion episode called Merge Conflicts Are Not Scary, and there are also related appendices on advanced Git and a VS Code reference. The authoritative references behind this lesson are GitHub Docs on resolving merge conflicts and the Git book&#39;s section on basic merge conflicts.</p></details>
     </article>