Rebuild HTML from updated markdown files

Author: GitHub Workshop Bot

html/CHALLENGE_SYSTEM_ARCHITECTURE.html

@@ -48,8 +48,8 @@ <h2>A Workshop by <a href="https://community-access.org">Community Access</a></h
 <td><a href="https://community-access.org/git-going-with-github/">community-access.org/git-going-with-github</a></td>
 </tr>
 <tr>
-<td><strong>Register</strong></td>
-<td><a href="https://community-access.org/git-going-with-github/REGISTER.html">Register for the workshop</a> (75 seats, free, two steps)</td>
+<td><strong>Registration</strong></td>
+<td>Closed - thank you to all who registered!</td>
 </tr>
 <tr>
 <td><strong>Discussions</strong></td>

html/README.html

@@ -31,7 +31,8 @@
   <main id="main-content" class="markdown-body">
     <h1>Registration Closed</h1>
 <p><a href="https://community-access.org/git-going-with-github/">Back to Home</a> | <a href="https://github.com/community-access/git-going-with-github/discussions">Discussion Forum</a> | <a href="https://community-access.org/git-going-with-github/docs/00-pre-workshop-setup.html">Pre-Workshop Setup Guide</a></p>
-<p>Registration for GIT Going with GitHub is now closed. Thank you to everyone who registered - let the learning begin!</p>
+<h2>Registration for GIT Going with GitHub is now closed.</h2>
+<p>Thank you to everyone who registered! We are excited to learn together.</p>
 <table>
 <thead>
 <tr>
@@ -41,7 +42,7 @@ <h1>Registration Closed</h1>
 </thead>
 <tbody><tr>
 <td><strong>Dates</strong></td>
-<td>Saturday, March 7 &amp; Sunday, March 8, 2026</td>
+<td>Saturday, March 7 and Sunday, March 8, 2026</td>
 </tr>
 <tr>
 <td><strong>Time</strong></td>
@@ -57,8 +58,36 @@ <h1>Registration Closed</h1>
 </tr>
 </tbody></table>
 <hr>
-<h2>Already Registered?</h2>
-<p>Complete the <a href="https://community-access.org/git-going-with-github/docs/00-pre-workshop-setup.html"><strong>Pre-Workshop Setup Guide</strong></a> before March 7. It walks you through GitHub account setup, screen reader configuration, <a href="https://code.visualstudio.com/">VS Code</a>, and <a href="https://github.com/features/copilot">GitHub Copilot</a> - with instructions for NVDA, JAWS, and VoiceOver.</p>
+<p><strong>Already registered?</strong> Complete the <a href="https://community-access.org/git-going-with-github/docs/00-pre-workshop-setup.html"><strong>Pre-Workshop Setup Guide</strong></a> before March 7. It walks you through GitHub account setup, screen reader configuration, <a href="https://code.visualstudio.com/">VS Code</a>, and <a href="https://github.com/features/copilot">GitHub Copilot</a> - with instructions for NVDA, JAWS, and VoiceOver.</p>
+<hr>
+<h3>Questions?</h3>
+<p>Need help? <a href="https://github.com/community-access/git-going-with-github/issues">File an issue</a> in the workshop repository or join the <a href="https://github.com/community-access/git-going-with-github/discussions">Discussion Forum</a>.</p>
+<p><em>A <a href="https://community-access.org">Community Access</a> initiative.</em></p>
+<p><strong>Important:</strong> You must be signed into your GitHub account before clicking the link below. If you are not signed in, go to <a href="https://github.com">GitHub</a> and sign in first.</p>
+<blockquote>
+<p><a href="https://github.com/community-access/git-going-with-github/issues/new?template=workshop-registration.yml&title=%5BREGISTER%5D+GIT+Going+with+GitHub+-+March+2026"><strong>Start Step 2 - File your registration issue</strong></a></p>
+</blockquote>
+<p><strong>Note:</strong> The issue title is pre-filled and required by GitHub. You do not need to change it - just fill out the form fields below it and submit.</p>
+<p>The form asks for:</p>
+<ul>
+<li><strong>First Name</strong> (required) - your first name as you would like to be addressed during the workshop</li>
+<li><strong>Last Name</strong> (required)</li>
+<li><strong>Email Address</strong> (required) - we will use this to send you Zoom links and workshop materials before the event</li>
+<li><strong>GitHub Proficiency Level</strong> (required) - a dropdown from &quot;Brand new&quot; to &quot;Experienced&quot; so we can prepare the right level of support</li>
+<li><strong>Primary Screen Reader</strong> (optional) - which screen reader you primarily use (NVDA, JAWS, VoiceOver, or other)</li>
+<li><strong>Questions or Accommodations</strong> (optional) - anything we should know or arrange before the workshop</li>
+</ul>
+<p>After you submit, you will receive an automated confirmation comment on your issue. Your GitHub username is captured automatically - you do not need to enter it.</p>
+<hr>
+<h2>What Happens Next</h2>
+<p>Once you have completed both steps:</p>
+<ol>
+<li>You will receive a Zoom confirmation email (Step 1)</li>
+<li>You will see a confirmation comment on your GitHub issue (Step 2)</li>
+<li>Complete the <a href="https://community-access.org/git-going-with-github/docs/00-pre-workshop-setup.html">Pre-Workshop Setup Guide</a> before March 7 - it covers GitHub account setup, screen reader configuration, <a href="https://code.visualstudio.com/">VS Code</a>, and <a href="https://github.com/features/copilot">GitHub Copilot</a></li>
+<li>Questions? <a href="https://github.com/community-access/git-going-with-github/issues">File an issue</a> in the workshop repository</li>
+</ol>
+<hr>
 <h2>While You Wait</h2>
 <ul>
 <li><a href="https://github.com/community-access/git-going-with-github/discussions"><strong>Join the Discussion Forum</strong></a> - introduce yourself, ask questions, and connect with fellow participants before Day 1</li>
@@ -72,5 +101,25 @@ <h2>While You Wait</h2>
     <p><strong>GIT Going with GitHub</strong> - A workshop by <a href="https://community-access.org">Community Access</a></p>
     <p><a href="https://github.com/community-access/git-going-with-github">View on GitHub</a> · <a href="https://community-access.org">community-access.org</a></p>
   </footer>
-</body>
+  <script>
+(function() {
+  var url = 'https://api.github.com/search/issues?q=repo:community-access/git-going-with-github+label:registration+is:issue+is:open';
+  var xhr = new XMLHttpRequest();
+  xhr.open('GET', url);
+  xhr.setRequestHeader('Accept', 'application/vnd.github+json');
+  xhr.onload = function() {
+    if (xhr.status === 200) {
+      try {
+        var count = JSON.parse(xhr.responseText).total_count;
+        var els = document.querySelectorAll('[id^="registration-count"]');
+        for (var i = 0; i < els.length; i++) {
+          els[i].textContent = count;
+        }
+      } catch (e) {}
+    }
+  };
+  xhr.onerror = function() {};
+  xhr.send();
+})();
+</script></body>
 </html>

html/REGISTER.html

@@ -76,8 +76,7 @@ <h3>Software - Day 1</h3>
 <h3>Software - Required Before the Workshop</h3>
 <ul>
 <li><strong>Git</strong> - <a href="https://git-scm.com/downloads">Download Git</a> (Windows/Linux) or Xcode Command Line Tools (macOS)</li>
-<li><strong>Visual Studio Code</strong> (free) - <a href="https://code.visualstudio.com/">download here</a></li>
-<li><strong>GitHub Copilot Chat</strong> extension for VS Code - installed from within VS Code (this single extension provides both inline suggestions and Chat)</li>
+<li><strong>Visual Studio Code</strong> (free) - <a href="https://code.visualstudio.com/">download here</a> (GitHub Copilot is included automatically)</li>
 <li>A GitHub Copilot subscription or Free tier access (Copilot Free is available to all GitHub users)</li>
 </ul>
 <h3>Screen Reader Options</h3>
@@ -691,66 +690,26 @@ <h3>Using the Correct Email</h3>
 <p>Use the same email you registered with GitHub. If you&#39;re concerned about privacy, GitHub offers a no-reply email you can use: <code>username@users.noreply.github.com</code> - find it in <a href="https://github.com/settings/emails">Settings → Emails</a>.</p>
 <hr>
 <h2>Step 8 - Install VS Code Extensions</h2>
-<p>This workshop uses two VS Code extensions. Both are published by GitHub and are free. Install them in the order shown below.</p>
+<p>This workshop uses two VS Code extensions. GitHub Copilot is built into VS Code automatically. The GitHub Pull Requests extension needs to be installed manually. Both authenticate through your browser session - if you are signed into GitHub in your web browser, VS Code picks up the session automatically.</p>
 <hr>
-<h3>Sign in to GitHub in VS Code first</h3>
-<p>Both extensions require you to be signed into GitHub. Do this once and both will be authenticated.</p>
+<h3>GitHub Copilot (Built In)</h3>
+<p>GitHub Copilot is automatically included with Visual Studio Code. There is no extension to install separately. It provides both inline code completions and the conversational Agent mode panel used throughout the second half of the workshop.</p>
+<h4>Activate Copilot</h4>
 <ol>
-<li>Open VS Code</li>
-<li>Press <code>Ctrl+Shift+P</code> to open the Command Palette</li>
-<li>Type: <code>sign in</code> and arrow down to <strong>&quot;GitHub: Sign in&quot;</strong> - press <code>Enter</code><ul>
-<li>Your default web browser will open to a GitHub authentication page</li>
-</ul>
-</li>
-<li>In the browser, confirm your GitHub account when prompted and select <strong>Authorize Visual Studio Code</strong></li>
-<li>Switch back to VS Code - your browser may ask you to confirm opening VS Code; select <strong>Open</strong> or <strong>Allow</strong></li>
-<li>You should hear VS Code announce a notification, and the accounts icon in the Activity Bar will show your GitHub username</li>
-</ol>
-<blockquote>
-<p><strong>Screen reader note:</strong> The authentication happens in your browser. After authorizing, your browser will show a page saying &quot;You can close this tab and return to VS Code.&quot; Switch back to VS Code with <code>Alt+Tab</code> (Windows) or <code>Cmd+Tab</code> (macOS).</p>
-</blockquote>
-<hr>
-<h3>Extension 1 - GitHub Copilot Chat</h3>
-<p>This single extension provides both inline code completions and the conversational Chat panel. It is used throughout the second half of the workshop.</p>
-<h4>Install</h4>
-<ol>
-<li>Press <code>Ctrl+Shift+X</code> to open the Extensions panel<ul>
-<li>Your screen reader will announce &quot;Extensions&quot; and place focus in the search box</li>
-</ul>
-</li>
-<li>Type: <code>GitHub Copilot Chat</code><ul>
-<li>The list updates as you type</li>
-</ul>
-</li>
-<li>Press <code>Tab</code> to move from the search box into the results list</li>
-<li>Arrow down through the results. Look for <strong>&quot;GitHub Copilot Chat&quot;</strong> with publisher <strong>&quot;GitHub&quot;</strong><ul>
-<li>There are similar-named extensions from other publishers - verify the publisher is &quot;GitHub&quot; before installing</li>
-</ul>
-</li>
-<li>Press <code>Enter</code> to open the extension details page</li>
-<li>Press <code>Tab</code> to find the <strong>Install</strong> button, then press <code>Enter</code> or <code>Space</code></li>
-<li>Wait for installation to complete - VS Code will announce &quot;Extension installed&quot; or similar</li>
-</ol>
-<h4>Verify it is working</h4>
-<ol>
-<li>Press <code>Ctrl+Shift+I</code> to open the Copilot Chat panel<ul>
+<li>Make sure Screen Reader Mode is enabled (see above)</li>
+<li>Make sure you are signed into GitHub in your web browser</li>
+<li>Press <code>Ctrl+Shift+I</code> to open Agent mode<ul>
 <li>Your screen reader should announce the chat input field</li>
 </ul>
 </li>
-<li>Type: <code>Hello, are you there?</code> and press <code>Enter</code></li>
+<li>Type: <code>Hello</code> and press <code>Enter</code></li>
+<li>VS Code will automatically sign you into GitHub Copilot using your browser session - no manual sign-in command is needed</li>
 <li>A response will appear in the chat history above the input field</li>
 <li>Navigate up with <code>Shift+Tab</code> or <code>Up Arrow</code> to read the response</li>
-<li>If you see an error about signing in, press <code>Ctrl+Shift+P</code> and run <strong>&quot;GitHub: Sign in&quot;</strong> again</li>
-</ol>
-<h4>Verify inline completions</h4>
-<ol>
-<li>Press <code>Ctrl+N</code> to create a new untitled file</li>
-<li>Press <code>Ctrl+Shift+P</code>, type <code>change language</code>, and select <strong>&quot;Change Language Mode&quot;</strong> - choose <strong>Python</strong> or <strong>JavaScript</strong></li>
-<li>Start typing a function name such as <code>function greet</code> (JavaScript) or <code>def greet</code> (Python)</li>
-<li>Pause for 1-2 seconds - Copilot will suggest a completion in grey ghost text</li>
-<li>Press <code>Tab</code> to accept it, or <code>Esc</code> to dismiss</li>
-<li>If no suggestions appear: confirm Copilot icon shows in the status bar and that you are signed in</li>
 </ol>
+<blockquote>
+<p><strong>That is it.</strong> You do not need to use the Command Palette to sign in. If you are logged into GitHub in your browser, VS Code handles authentication automatically when you first interact with the agent.</p>
+</blockquote>
 <hr>
 <h3>Extension 2 - GitHub Pull Requests</h3>
 <p>This extension lets you review and manage pull requests without leaving VS Code. It is used in the code review chapters.</p>
@@ -817,10 +776,8 @@ <h2>Step 9 - Verification Checklist</h2>
 [ ] Git identity configured (git config --global user.name and user.email)
 [ ] Visual Studio Code installed
 [ ] Screen Reader Mode enabled in VS Code (Shift+Alt+F1 or Command Palette)
-[ ] Signed into GitHub in VS Code
-[ ] GitHub Copilot Chat extension installed (publisher: GitHub)
-[ ] Copilot Chat responds in the Chat panel (Ctrl+Shift+I)
-[ ] Copilot inline suggestions appear when typing in a file
+[ ] Signed into GitHub in your web browser
+[ ] GitHub Copilot responds in Agent mode (Ctrl+Shift+I, type Hello, get a response)
 [ ] GitHub Pull Requests extension installed (publisher: GitHub)
 [ ] Pull Requests panel opens (Ctrl+Shift+P → &quot;Focus on Pull Requests View&quot;)</code></pre>
 <hr>

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

@@ -96,6 +96,30 @@ <h3>Learning Pattern Used in This Chapter</h3>
 <li>Leave clear evidence in the issue timeline.</li>
 <li>Build momentum for PR work in Chapter 5.</li>
 </ol>
+<hr>
+<h2>Local Git Alternative: Working from Your Clone</h2>
+<details>
+<summary>If you cloned the learning-room in Block 0 and prefer working locally</summary>
+
+<p>During Block 0 you cloned the Learning Room repository to your computer. If you are comfortable in a terminal, you can use the GitHub CLI (<code>gh</code>) from inside that clone for every issue operation in this chapter. This is the same workflow covered in depth in <a href="11-git-source-control.html">Chapter 11: Git and Source Control</a>.</p>
+<p><strong>Verify your clone is ready:</strong></p>
+<pre><code class="hljs language-bash"><span class="hljs-built_in">cd</span> ~/Documents/learning-room   <span class="hljs-comment"># or wherever you cloned it</span>
+git status                      <span class="hljs-comment"># should show &quot;On branch main&quot;</span></code></pre>
+<p><strong>Common issue commands from your local terminal:</strong></p>
+<pre><code class="hljs language-bash"><span class="hljs-comment"># List your assigned challenge issues</span>
+gh issue list --assignee @me --label challenge
+
+<span class="hljs-comment"># View a specific issue in the terminal</span>
+gh issue view 42
+
+<span class="hljs-comment"># Leave a comment on an issue</span>
+gh issue comment 42 --body <span class="hljs-string">&quot;I&#x27;d like to try this!&quot;</span>
+
+<span class="hljs-comment"># Create a new issue interactively</span>
+gh issue create</code></pre>
+<p>All of these produce the same result as the web interface. The chapter instructions work identically either way - choose whichever is more comfortable for you.</p>
+</details>
+
 <hr>
 <h2>What Is a GitHub Issue?</h2>
 <p>An issue is a discussion thread attached to a repository. Issues are used for:</p>

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

@@ -91,6 +91,37 @@ <h3>Why this feels achievable</h3>
 <li>Feedback is immediate and specific.</li>
 <li>Success is visible (green checks + closed issue).</li>
 </ul>
+<hr>
+<h2>Local Git Alternative: The Full Branch-Edit-PR Workflow</h2>
+<details>
+<summary>If you cloned the learning-room in Block 0 and prefer working locally</summary>
+
+<p>The web editor workflow (pencil button, &quot;Propose changes&quot;) is the primary path taught in this chapter. If you cloned the Learning Room in Block 0 and are comfortable in a terminal, here is the local equivalent. This is the same workflow covered in depth in <a href="11-git-source-control.html">Chapter 11: Git and Source Control</a>.</p>
+<p><strong>Step 1 - Sync and create a feature branch:</strong></p>
+<pre><code class="hljs language-bash"><span class="hljs-built_in">cd</span> ~/Documents/learning-room
+git checkout main
+git pull origin main
+git checkout -b fix/welcome-todos</code></pre>
+<p><strong>Step 2 - Edit the file in your editor:</strong></p>
+<p>Open the file in VS Code or your preferred editor:</p>
+<pre><code class="hljs language-bash">code docs/welcome.md</code></pre>
+<p>Make your changes and save the file.</p>
+<p><strong>Step 3 - Stage, commit, and push:</strong></p>
+<pre><code class="hljs language-bash">git add docs/welcome.md
+git commit -m <span class="hljs-string">&quot;Complete TODO sections in welcome.md&quot;</span>
+git push -u origin fix/welcome-todos</code></pre>
+<p><strong>Step 4 - Open a pull request:</strong></p>
+<pre><code class="hljs language-bash">gh <span class="hljs-built_in">pr</span> create --title <span class="hljs-string">&quot;Complete TODO sections in welcome.md&quot;</span> \
+  --body <span class="hljs-string">&quot;Closes #42&quot;</span> --base main</code></pre>
+<p>Or open interactively:</p>
+<pre><code class="hljs language-bash">gh <span class="hljs-built_in">pr</span> create</code></pre>
+<p>The GitHub CLI walks you through title, body, base branch, and reviewers.</p>
+<p><strong>What happens next is identical:</strong> the Learning Room bot validates your PR, posts feedback, and you request a human reviewer - the same as the web workflow.</p>
+<blockquote>
+<p><strong>Tip:</strong> You can also use your <code>username-practice</code> branch instead of creating a feature branch. Switch to it with <code>git checkout username-practice</code> (replacing <code>username</code> with your GitHub username, all lowercase).</p>
+</blockquote>
+</details>
+
 <hr>
 <h2>What Is a Pull Request?</h2>
 <p>A pull request (PR) is a proposal to merge changes from one branch into another. When you have:</p>