Skip to content

Update section on configuring GitHub Pages #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alex-ball wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update section on configuring GitHub Pages #195

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e0dbffd
Fix typo
alex-ball Dec 9, 2025
f52d390
Update section on configuring GitHub Pages
alex-ball Dec 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions episodes/05-github-pages.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,23 +50,23 @@ Go to the Pages section of your repository's Settings:

![](fig/github-repo-settings-pages.png){alt="GitHub repository's Pages settings"}

#### Source branch (required)
#### Source and branch

Pages needs to know the branch in your repository from which you want to serve your site. This can be any branch, including `main`.
Pages gives you a choice between using the built-in Jekyll tool for building your website or providing your own tool.
We're going to use Jekyll, so leave the "Source" setting on its default value, "Deploy from a branch".

Select then save the source branch:
Jekyll needs to know the branch and folder in your repository from which you want to serve your site.
There are no particular restrictions here. This means we could develop a resource in one branch or folder, and maintain a website to describe it in another.
But on this occasion, we'll only use the repository for the site.

Select `main` as the branch, "/ (root)" as the folder, and then save these values:

![](fig/github-repo-settings-pages-branch.png){alt="GitHub Pages source branch menu"}

![](fig/github-repo-settings-pages-save.png){alt="GitHub Pages source branch save"}

#### Theme (optional)

GitHub Pages provides different themes to visually style and organize your site's content. Choosing a theme is optional, and themes can be interchanged quickly.

![](fig/github-repo-settings-pages-theme.png){alt="GitHub Pages choose theme"}

See the [GitHub Pages documentation](https://docs.github.com/en/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser) for further information on using themes.
That's all the configuration we need to get started with GitHub Pages, but there are other things you can change, such as the theme used to visually style and organize your site’s content.
If you want to explore further after the lesson, see the [GitHub Pages documentation](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll).

### View your site

Expand Down Expand Up @@ -241,7 +241,7 @@ you can use the fork you created there and skip to step 3.
remote:
```

You can visit that link in your browser, but if you go back to your fork in GitHib
You can visit that link in your browser, but if you go back to your fork in GitHub
you will also see a button has appeared that says "Compare & pull request".
You can click on that button instead if you prefer.

Expand Down