Update section on configuring GitHub Pages

[alex-ball]

The current text in Episode 5 for enabling GitHub Pages is written to suit the previous configuration screen. It therefore does not reflect the current screenshots to the extent we'd hope in terms of accessibility.

The proposed text here mentions the new form controls:

• "Source" now chooses between Jekyll ("Deploy from a branch", default, what we want) and GitHub Actions.
• The new "Branch" controls make you select both a branch and a folder.

I've added an explanation of why one might choose something different from what we say here.

There is no longer an option to choose the theme, so I've replaced the section that described it with a short paragraph. I retain the explanation of what a Jekyll theme does and the link to further information, but make it clear that configuration of that sort isn't part of this lesson (the unmentioned reason being that it involves creating and editing a YAML configuration file).

Closes #180.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/LibraryCarpentry/lc-git/compare/md-outputs..md-outputs-PR-195

The following changes were observed in the rendered markdown documents:

 05-github-pages.md | 22 +++++++++++-----------
 md5sum.txt         |  2 +-
 2 files changed, 12 insertions(+), 12 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-12-09 11:47:25 +0000

[srerickson]

This looks good to me! (One of my 2026 goals is to do more than just approve/review your PRs!)