Creating a Lightweight Blog with Github-Pages and Jekyll

As a developer I find the typical flow ant tools used for blogging to be less than ideal. I want a flow that embraces the tools I use on a daily basis and makes it as easy as possible to blog...

What I want is an optimized blogging platform and experience targetted to developers.

What about Wordpress?

I could have used Wordpress and WP Engine, an excellent solution to be sure. But, it doesn't really tick the developer flow or simplicity requirement.

GitHub to the Rescue

Github has a great feature called Github Pages that allows us devs to host static content as a web site - they even allow us to associate a custom domain name (e.g. with the web site. Could this be suitable?

GitHub Pages offers the following capabilities that are relevant to us:

Building the GitHub Pages Blog

So with this information, I decided to MVP blog using GitHub Pages and see how it went.

I decided to use the Hyde repository as a starting point as it looked quite beautiful and was simple to understand and enhance.

Cloning the Base Repository

If you don't already have a GitHub account, jump over there now and create one for free.

Once you're logged into your GitHub account, the quickest way to get started is to clone an existing Jekyll repository to modify. As stated, I decided to use Hyde, so to do the same, visit the Hyde repository and click the Fork button Hyde Repository Fork

There are other Jekyll repos you can clone to get started quickly. Check out JekyllNow and Poole for tsraters.

Rename your Cloned Repository

This step is critical! It's also easy :)

In the cloned repository, click the Settings button and then rename the repository so it has exactly the same name as your GitHub home. For me that's "", for you, it'll follow the pattern "".

Hyde Repository Fork

Visit your Cloned Blog

Your should now be able to visit your blog website at "".

Hyde Repository Fork

Customising your Blog

Now that you have a static blog, we'll customise it over the next few blog posts.

Things we'll be looking at customising: