GitHub Pages — A Comprehensive guide w/ images (Part 1)

GitHub Pages — A Comprehensive guide w/ images (Part 1)

Recently I started building my personal website as everyone is building for themselves these days. I got a cool TLD (.xyz), and that is the only money I wanted to spend. Since then I’ve been looking for ways to host it without any costs.

I’ve tried different host providers such as Heroku, 000webhost so far, which are good options. My website is vastly static pages so far until I figure out how to have a cms such as Ghost to be integrated with Gatsby for adding content periodically (Of course for free). Anyways I thought if my site is mostly static pages so why not give Github Pages a try (it’s been on my list for a quite sometime now) and along the way I encountered various hurdles and there wasn’t an elaborate article around it. So folks here we are :)

This is part 1 of this article series, part 2 can be found here. Enchanté.

Setting up Github Pages:

This is the most straight forward thing, it’s all neatly illustrated here on Github Pages, but as this article‘s name suggests I’m bound:

We’ll start by creating a repository on Github:

  1. Goto, a cooler way to create Github repositories (You’ll see).

Make sure your repo-name is The pages ending with are called User Pages, where could belong to an individual or an organization

Repository creation flow on GitHub
Repository creation flow on GitHub

Note: It is important to make your repository Public, in order for your GitHub User pages to be accessible to all

We won’t be creating any other branch, because User Pages require to be built from master branch. And in this article, we won’t use Jekyll to publish our pages.
  1. First clone the repo to local machine: Here, <username> is GitHub username
~$ git clone
  1. Create an index.html file inside this repository:
~$ cd

~$ echo “Hello World!!” > index.html
  1. Add, commit and push your changes to Github remote:
~$ git add *

~$ git commit -m "Initial commit"

~$ git push -u origin master
  1. Type {<username> } in browser and you’re done publishing your first website to github pages.
Browser screenshot of deployed Github pages
Browser screenshot of deployed Github pages

Setting up Github Pages on your custom-domain:

We have successfully created and deployed Github Pages. But I want users to visit my custom domain Lets link’em up:

  1. Created a CNAME file in your repository: I will be doing it via GitHub UI, just create a CNAME file (with no extension) and just enter your domain name inside it, nothing else.

Once Done, commit your changes.

Adding CNAME file to repository
Adding CNAME file to repository
  1. Change DNS records on your DNS provider: We need to change existing CNAME records to point to created github pages i.e. <username>
Changing CNAME records on Cloudflare
Changing CNAME records on Cloudflare

Important Points:

  • At this point, nothing needs to be done from our end, we need to wait for changes to reflect on both GitHub and Cloudflare end, Which may take some time (usually its prompt) but may take some time based on your DNS provider
  • You won’t be able to access your pages via, in case you try and enter this in browser, you’ll be redirected to your custom domain
Github Page deployed on custom-domain
Github Page deployed on custom-domain

So this was all to get you started with your very own Github Pages (User). In Part 2 of this series we’ll be taking deeper look into gh-pages and linking pages to your sub-domain.

Part 2 is now available here. Happy Building!!

Original article on: