What is GitHub Pages?
GitHub Pages is a feature of GitHub (a cloud service for storing code) that lets you publish the HTML files in a repository (a folder) directly as a website. It's free for static sites with no ads. You get a URL like "username.github.io" and can also configure a custom domain. Engineers around the world use it to publish portfolios and documentation.
Overview of the publishing process
① Create a GitHub account
Go to github.com and create a free account with your email and a password. Users must be 13 or older (under 13 requires parental consent). Your username becomes part of your public URL, so a nickname is recommended over your full real name.
② Create a repository
Click "New repository" to create a repository (like a folder). If you name it "username.github.io," you get a special URL (https://username.github.io/). Any other name also works, but the URL will be longer (https://username.github.io/repo-name/).
③ Upload index.html
From the repository, go to "Add file" → "Upload files," drag your index.html and CSS files in, and save (commit). If you know the command line, git push achieves the same thing.
④ Enable Pages
Go to Settings → Pages, select the source branch (usually "main"), and save. Wait 1–2 minutes, then visit the URL — your site should appear. At this point, anyone in the world can access it.
If the page doesn't show up, first check the filename of index.html, the repository name, and the source branch selected in Pages. GitHub Pages is case-sensitive, so Image.png and image.png are treated differently and images can fail to load. Updates can also take a moment to propagate after you push.
Before publishing real names, school names, addresses, or face photos, always talk to a parent/guardian or teacher. GitHub Pages is convenient for practice, but a published page can spread through search and social media. Starting with fictional profiles or portfolio work only is the safe approach.
What GitHub Pages can and can't do
Common pitfalls
- The repository must be "Public" to use Pages for free — which means your code is visible to everyone. Private repositories require a paid plan.
- Never push passwords, API keys, or personal info in code. On a public repo, the whole world can read it.
- Watch file name capitalization. A file that works on your PC may show 404 on GitHub because
Image.png≠image.png.
How will this help you in the future?
Using GitHub is the "reading and writing" baseline of the software engineering world. The experience of publishing a site with GitHub Pages is also an introduction to Git and GitHub — directly useful for future team projects and job applications. "Your own GitHub account" is often looked at more than a resume in the engineering world.
Publishing work builds more than coding skills: writing clear descriptions, keeping a commit history, fixing broken links. When it's time to build a portfolio, showing both a live URL and the source repository lets anyone verify and inspect what you built.
What you can do today
- Check GitHub’s age rules with a parent
- Put index.html in a repository
- Turn on Pages and write down the URL
Summary
Check GitHub Pages is for?