GitHub Pages is a free static site hosting service built into GitHub. Once you turn it on for a repository, GitHub takes the files you have committed — HTML, CSS, images — and serves them at a public web address that anyone can visit. There is no server to rent, no FTP client to configure, and no build server to maintain: publishing is simply a matter of pushing your work to the right branch and folder.
This matters in COP4813 because GitHub Pages is the delivery end of the workflow you will repeat all semester. You will edit files locally, commit and push them to GitHub, and then confirm the change appears on your live site. Understanding that the URL is derived from your username and repository name, and that GitHub rebuilds automatically after each push, removes most of the mystery when something does not appear as expected.
As you watch the videos below, pay close attention to three things: where the Pages settings live in the repository (Settings, then the Pages section), which branch and folder are selected as the publishing source, and the exact shape of the resulting URL. Also notice that publication is not instant — there is a short build delay, so a page that looks missing may simply need a refresh a minute later. Interfaces change over time, so expect small differences between what you see on screen and GitHub's current layout; the underlying steps remain the same.
A step-by-step walkthrough of hosting a website on GitHub Pages, from repository setup through to a live, publicly reachable site. At roughly fifteen minutes, it has room to explain the reasoning behind each step rather than just clicking through, and to show the published result in a browser.
The longer format makes it the best choice for students who want the full picture of what GitHub Pages is and how the publishing process works, covering enabling Pages, the resulting URL, and verification in one continuous demonstration.
A fast, focused tutorial that builds a simple portfolio site and publishes it with GitHub Pages in about five minutes. It emphasizes the practical path from an empty repository to a shareable public link you can show employers or clients.
With over 170,000 views, this is a widely used quick reference that cleanly demonstrates enabling Pages and obtaining a live URL — useful as a concise review after the longer walkthrough, and a reminder of why a public link is worth having.
A short, recent guide to hosting a website on GitHub for free using GitHub Pages, showing the key clicks needed to turn a repository into a published site. Its brevity means it concentrates on the essential settings and the resulting address.
Being the most recent of the three, it is likely to reflect a GitHub interface closest to what you will see today, making it a helpful cross-check if the menus in the other videos look unfamiliar.
Together these videos support MO1 by demonstrating the full configuration path from repository to enabled GitHub Pages deployment, and MO3 by showing the push-then-verify habit of checking the live site in a browser after publishing. They reinforce MO4 by making visible how GitHub detects committed changes, rebuilds, and serves the result at a username-and-repository-based URL, and they illustrate MO5 by placing local files, the GitHub repository, and the published site side by side as three distinct stages of one pipeline. While they do not teach HTML structure directly (MO2), they give you the hosting destination where the minimal HTML document you build in this module will be published and verified.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.