##Blogging with github.io, Jekyll, and your own domain name
Your Own Blog
Blogs are an important way to market yourself, knowledge and skills. I won’t go into detail because I’ll assume that if you’re reading this, You’re interested in creating a blog.
The blogging platform being used in this tutorial is Github. Normally most wouldn’t consider Github a blogging platform, however Github has set up a domain “github.io” for developers to use for personal or project blogs. You can have one blog per account, and one blog per project. We’ll be using the account blog.
The benefit to using github is the free hosting, and being hosted on github your blog will never go down unless github itself goes down, and in that scenario you’ll more likely be worried about your inability to push code or work than people reading your blog. In addition using the Jekyll platform is simple and allows you to pump out blog posts without requiring you to mess with a database or use a login: just have a github account, which if you’re reading this you most likely have already.
Your Username.github.io Repo
The first step to setting up a Jekyll based blog is to find a Jekyll theme you want to use. Head over to Jekyll Themes and find a theme you’d like to use. For my blog, and this tutorial, I decided to use Strange Case Go to the themes page on github and fork the repo to your own repo. You’ll want to name the repo yourusername.github.io. Make sure the default branch is Master.
Master should be the default branch because you’re creating an account blog. This is an important point other tutorialsI’ve seen on github blogging fail to mention. The gh-pages branch is used by project page blogs. If the repo you forked doesn’t have a master branch we’ll create it in the next section.
Now what you’ll want to do is clone your repo to a local dev environment. This is so you can edit your posts and view them on the localhost server before making them public on Github. Install Ruby if you don’t already have it (if you have a Mac, it’s there already). After you’ve cloned your forked of the theme (yourusername.github.io) to your local dev env, now’s your chance to create the master branch if it didn’t exist (git checkout -b master) The next thing you’ll want to do is install a tool called Ruby Bundler Ruby Bundler is gem manager for Ruby projects. You can think of it as something similar to pip for python or npm for node.js After installing Bundler, you’ll make use of it by createing a file named simply ‘Gemfile’ A Gemfile will contain one or more source declarations and one or more gem declarations to be used in your project. Here’s an example:
source 'https://rubygems.org' gem 'github-pages'
Run ‘bundle install’. This will install the gem in your gemfile, which is required to host Jekyll on Github. Now try running the Jekyll server local. Run the command ‘bundle exec jekyll serve’. Which essentially runs the ‘jekyll serve’ command but requiring all gems in the gemfile ‘jekyll serve’ will launch a Jekyll serve on port 4000 of the localhost, so open a browser and go to http://localhost:4000 and you should see your running Jekyll blog.
Make sure you set the correct config options in the _config.yaml file. If your going to use a custom domain, which I did, set base url to nothing. New posts are created by dropiing a readme file in the _posts directoy. Name a post with this convention ‘YYY-MM-DD-post-name.md’ You will need to add important metadata at the top of each post file. Here’s an example, the metadata for this post:
--- layout: post title: Blogging with Jekyll and Github date: 2014-01-12 20:00:00 categories: tech featured_image: "/images/posts/1/bg.png" published: true ---
The rest is just adding text in Markdown.
Custom Domain with Your Blog
I’m using my own domain to point to my blog. I use Godaddy as a registrar, so I create a file called ‘CNAME’ in my repo and add my domain to it
I log into godaddy and change my @ record to point to either 18.104.22.168 or 22.214.171.124 Make sure to change your project website url of your username.github.com repo to point to your domain name. Now push all of your changes to Github. It could take up to 30 minutes for your content to show up.