Hi there! 2017 is nearing its end, and well, while we celebrate the wonderful memories of this year, it's also time to reflect on the past year and come up with resolutions for the New Year. I'm happy that I've managed to keep this blog alive. It all started in the year 2015 when I started this blog, and it's been glorious 3 years of blogging. If you've been following my blogs, I hope you found them useful all along.
I'm planning to completely overhaul my blogging platform for the new year. All that would remain the same are the published articles, but all else is about to change. Well, there are 2 main reasons why I feel this overhaul is necessary.
A fresh look provides a fresh perspective and provides a change from the monotony
(The main reason) The new platform will help me reduce the maintenance costs of the blog (better invested in some other pursuits)
Now, before I share details on the new blogging platform, I would like to share some details on my earlier blogging platform setup.
Previous blogging platform setup
Hosting my blog on WordPress was worth it when I had just begun blogging. It had very good usability, a variety of quality blog themes and a plethora of plugins to make it easy to add features to your blog. I loved the markdown plugins they provided (which also helped me to migrate my posts to the new platform effortlessly).
While maintaining this blog I realized that certain features are crucial if you are serious about blogging.
Some must-have features in a blogging platform
Good server uptime
Fantastic collection of cool themes and nifty plugins
Markdown support is a bonus
Ability to capture user Comments on the blog posts
Reasonable purchase and renewal costs to maintain the blog year on year.
Ability to migrate your content to a new platform, should the need arise in the future.
My WordPress blogging platform on BigRock provided all of this. However, the annual maintenance cost was about 5 times the website domain cost. Now, I had 2 options - either think of some ads monetization approach to cover up the costs or think of an alternative to help curb the costs.
Owning a domain is necessary, and when your existing provider's service is good, it makes sense to stay with them. So this left me with the option to check if there are alternate hosting options. This is when I came across GitHub Pages and Jekyll.
What are GitHub Pages and Jekyll?
Let's try to understand both of these and how they are used.
GitHub Pages is a web hosting service offered by GitHub for hosting static web pages. It is integrated with the Jekyll software for static website and blog generation.
Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites.
Think of Jekyll as a file-based CMS, without all the complexity. Instead of using databases, Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by a web server.
In a nutshell,
Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories.
The last part about hosting the website from your GitHub Repositories is the crux here. It means that as long as you are fine with having your website content in a public repository you can host it for free (no charges). Of course, if you have some sensitive data and plan to keep your website content private you can use GitHub's private repositories. But then you need to pay the appropriate costs.
Does Jekyll support themes?
Yes, Jekyll does support themes. There are several free and paid Jekyll themes available online. You could check out a few of these here.
How to install and deploy using Jekyll?
If you are using windows, you can follow the steps here to install Jekyll and deploy your website using it. Note that Windows is not an officially supported platform for Jekyll. However, some tweaks are used which you could get done. On the contrary, it is beneficial if you are using Windows 10 64-bit OS with Windows Subsystem for Linux (WSL) activated. That way, you can use the bash command line to install Jekyll. If WSL is new to you, you might want to check my earlier post that explains it in detail.
If you are creating a new blog from scratch, then this should be painless. However, if you plan to migrate your existing blog to this platform, then there could be a few challenges. I was lucky to have used markdown syntax for all posts on my wordpress hosted site. So migration was super easy. However, I did lose out on the comments posted on my blog posts. Looking back, there could have been a way to migrate those as well, but I did not wish to invest more time there.
So before you take the plunge I would suggest you try creating a sample website using this platform, and once you get familiar with it, analyze whether it would be beneficial in your case.
Hope this was useful!!