Forcing HTTPS on your static blog

Google started using HTTPS as a ranking signal, which means that adding HTTPS to your site will give you a better Google ranking score. If you want your blog to benefit from that, you can turn on HTTPS - and optionally redirect HTTP to HTTPS. A very easy way to do this is with Cloudflare. If you move your DNS nameservers to Cloudflare, you can leverage their SSL features. After moving to Cloudflare, turn on “Flexible SSL” for your domain. After a short while you will be able to access your site on HTTPS.

Continous delivery of Jekyll blog to with Codeship

Now that the blog has been created, it is time to setup continuos delivery. The goal of setting this up is to be able to just push new changes to the master branch in Bitbucket and the blog will automatically be deployed to surge.

Creating a blog with Jekyll, Poole and

I wanted a place to write down my notes and experiences with various technologies. Since I like learning new technologies I decided to pick a technology I had no prior experience with. This is Jekyll. Jekyll is an engine that helps generate a static website from your Markdown text files (it also understands other formats, but I will use Markdown for my blog posts). Since the site is built with Jekyll, the blog posts will be stored as text files. This makes them an ideal fit for a source control system - like Git. You can actually host your blog for free with Github Pages, which is powered by Jekyll. However that requires a public repository on Github. This is not necessarily a problem, and will work well for many blogs and projects. It could also work for my blog, but I decided to go down a different path.