code.Antrikshy | Notes, tinkerings, experiments

The Absolute Noob Guide To Hosting A Personal Website Or Blog On GitHub Pages - Part 3

So you have decided to use Jekyll as your website engine of choice. It makes themeable, efficient websites that can be hosted on a traditional web server without the need for computation in the cloud, the hassle of databases etc.

Working On Your Website

You have a few options at this point.

  1. Blank Jekyll website. Roll a vanilla site and customize the pages to your heart’s content.
  2. Themed Jekyll website. While you can install themes later, it is a bit of a hassle to do so. It involves manually adding and replacing the folders that come with a basic Jekyll project, leaving your content alone. It’s just a nice idea to pick a theme for now and go with it.
  3. A forked Jekyll project. People have modified Jekyll to create their own variants. Some come with beautiful layouts and have their own themes. My Jekyll flavor of choice is Poole. There is also Jekyll-Bootstrap, built on the Bootstrap framework.

I would suggest going with one of the forked projects. They generally come with a bunch of modifications that will make your life easier. They usually come with their own installation and modification instructions, which is great!

While you don’t need to be a web design guru to make your blank website and customize it, you will certainly need some work to make it look different from other basic Jekyll websites.

Blank Jekyll Project

You can generate a blank Jekyll website by going to your folder using cd and typing

jekyll new .

Tip: The dot refers to the current folder, so the new website is created in the current folder.

This creates a bunch of files and folders inside your GitHub Pages folder. You can use ls to see them, or you can simply navigate to the folder in Finder, Windows Explorer or whatever file management system you use.

To see what this empty website looks like, you can use the command

jekyll serve

jekyll serve

This will create the virtual server that I was talking about earlier. You can open a web browser and type in localhost:4000 as the address. This will show you a blank Jekyll site that looks like this:

New Jekyll site

Now you can dig into its folders and modify the files to personalize the website.

Themed Or Forked

Whether you want to choose a themed Jekyll or a modified Jekyll instance, you will need to download the Jekyll project from a website instead of using the jekyll new command. Just place these files inside your GitHub Pages folder.

When I downloaded Poole, I just downloaded a zipped folder of this GitHub repo (using the button on the right) and placed its contents inside my folder.


Anatomy Of A Jekyll Website

You have now set up a Jekyll website. The internals of the website may vary based on the version you download, so you should check the required documentation yourself. But I can certainly go over the bare minimum basics of a Jekyll website.

Jekyll allows you to create page layouts. This means that you can design new page layouts in the _layouts folder. Some forks of Jekyll may come with layouts for special pages already. Think of layouts as scaffolding for a certain type of page on your site. If you decide to create a bunch of pages that have a similar design, you can rely on a layout feature. Check out the layouts included in the _layouts folder to get a feel for them. You can include the same tidbit written in HTML or Markdown inside layouts, so they show in all the pages that inherit from that layout. They include variables that are explained in Jekyll’s documentation.

Here are some files and folders that you should know about:

You can also create a _drafts folder to hold unpublished content. When you run the serve command with the --drafts argument like so…

jekyll serve --drafts

…the virtual server will include your drafts so you can see what your post will look like when published. You can leave unpublished articles inside the _drafts and sync the site without worrying about unfinished content showing up to your readers.

Writing Posts

I do not have too much experience with stock Jekyll as of this writing. I may update this guide at a later point if I do play around with it. I only started off with Poole, which configured much of the website for me.

What you get with jekyll new . is a basic website with a homepage that lists all your posts. You can play around with the index.html file in the root folder to arrange this homepage differently. Either you choose to go with a stock installation of Jekyll or some customized or themed version created by someone else, blog posts are created in the same way.

To create posts:

  1. Write a post in Markdown. You can use any text editor of your choice. You can draft posts as described in the previous section to see what they look like on the website.
  2. Place the post in the _posts folder.
  3. To publish articles, you need to save the file with a certain naming format. This format is For example, I have named this post The title does not have to match the actual title of the article (I will show you how to set that later). The title in the file name is used to link to said post from other posts in the website. This way, all internal links will continue to work even if you change domains or rearrange your Jekyll project later. Jekyll’s documentation describes this in detail.
  4. Add YAML Front Matter at the very top. This Jekyll docs page explains it. Basically, this bit describes to the Jekyll engine what the file contains. The layout attribute makes sure that the post scaffolding gets applied to the page. Same goes for any other page you create on the website. The title attribute is what gives the post its title.
  5. Sync the website with GitHub.

Jekyll Tips

I will probably add points here as I learn more about Jekyll.

Use the --watch argument when using jekyll serve to rebuild the website every time changes are made. This way, as you make changes to any of the files that make up the website, the virtual server will instantly update changes. You can refresh the localhost:4000 to see changes almost live. For best results, use

jekyll serve --drafts --watch

Custom Domain Name

Now that you have a website up and running at a free domain like, you may want to have a custom domain name like or point to it. This is very easy to do. Simply buy a domain name. I use and recommend Namecheap myself. They have competitive pricing and are very easy to use. They don’t spam you with emails later and have various support options in case you need help.

This guide walks you through the instructions for Namecheap, although it should be similar for other services.

Configure Top-Level Address

  1. Create a new file in your folder. Call this file CNAME, without any extension. In this file, add a single line:,, or whatever URL you want to point to this website.
  2. In your Namecheap ‘Manage Domains’ page, click the domain you want to point to your GitHub Pages site. Go to the ‘All Host Records’ page for this domain.
  3. Set the IP Address/URL for @ to and the Record Type to A (Address).
  4. Set the IP Address/URL for www to *username* and the Record Type to CNAME (Alias).
  5. Under Sub-Domain Settings, set the first field to @, its IP Address/URL to and its Record Type to A (Address).
  6. Set all TTL fields to 1800.

Configure Subdomain

  1. Follow steps 1 and 2 above.
  2. Set the first field under Sub-Domain Settings to whatever subdomain you want to point to your GitHub Pages site. This can be ‘blog’ if you want to point to your site.
  3. Set its IP Address/URL to *username* and its Record Type to CNAME (Alias).

If these steps do not work, ask me in the comments. I set my ‘blog’ subdomain to this site, but my personal site is hosted on Amazon S3, so I used Amazon’s Route53 to configure everything. I might explore this in a future post.

Where Do We Go From Here

I set my website up using this excellent guide by Joshua Lande. His post may have some nifty tips that you may find useful. He has a more detailed explanation about customizing page layouts.

GitHub’s support has a ton of documentation for configuring your GitHub Pages site. It is more geek-oriented, but it has detailed explanations.

Jekyll’s documentation has instructions for composing posts, adding images, file downloads and more.


Please submit any feedback in the comments and I will try to respond to them very quickly. I have never done a technical blog like this one and this is one of the first posts I ever made. Therefore, some things may not be too clear.

Talk to me via Twitter and check out my stuff on GitHub.