Skip to main content
  1. Posts/

Blogging in the Hard Way

I have started this blog in last November, after that I did not write anything, as like the way it happens every time. We start something and forget, until we make it as routine. Meanwhile, I was doing some analysis and checks, etc on the blogging platform. Like to share the same here..

Most of the contents updated in this post aren’t relevant today, as I have migrated this blog from Hexo to Hugo platform, for some reason. Fore more info visit the github repository where the contents are hosted.

The Static Blog Platform #

Why Static Blog? I have tried using the ready-made blogging platforms such as Blogger, WordPress, etc., But I settled with Static blogging platform, for its simplicity and speed, also I want to try something in a hard way to make it work (Actually setting up a static blog is not that hard).

I can write posts when I am off line, using a notepad++. Then just push to git repository when I connected to Internet. Git provides the history / version control for all the modifications that I do. If I feel a change that I made recently not working, I can just use git revert command to go back to the previous state.

I have tried different static site generators the order listed below:

  • Jekyll - Lot of themes available, Github build the pages automatically. But, felt it is slow. Still my primary domain page is running on Jekyll. Edit: Moved to static page now.
  • Hugo - Simple. But Hexo won my heart.
  • Ghost - Subscription based, not my cup of tea.
  • Hexo - The Winner!! though most of the users are from china, thanks to Google translate
  • Gatsby - The post title would have changed to the Hardest way, if I have used Gatsby.

I have tried all the platforms finally settled with Hexo for the speed and the vast number of plug-ins. Github pages automatically build pages, if I use Jekyll. I need a CI to build the site, or I need to deploy it from my PC whenever I write a post using Hexo. I have tried different CI such as Travis-CI, Circle-CI, Netlify, Gitlab CI, etc.,

Domain #

I have purchased this domain from Google Domains. I pay $12 per annum for it, which is the only service that I pay money when setting up this blog.

Still thinking of moving it to a different domain name, which can be easily remembered. I know the the word ‘anbuchelva’ would be hard to pronounce who are not from South India.

Hosting #

The next question that arise in your mind, what about hosting? Aren’t you paying any money for it? The answer is yes. I’m not paying anything for hosting, as I host it in Github pages

There are few alternates available such as Gitlab Pages, Bitbucket, Netlify, etc., I have settled with Github Pages + Cloudflare for hosting and CDN services. Github pages provide very fast server response than the others that I have listed above. This improves the Google page speed drastically.

Still thinking of moving the source of this blog to Gitlab or Bitbucket for privacy and host the pages that are built in Github. Github doesn’t offer Private Repository services for free. Few differences when comparing Gitlab and Github.

Private RepositoryUnlimited private repositoriesNot available
Continuous Integration2000 Hours of CI engine per MonthNot available,
have to depend on other CI cervices like Travis-CI, Circe-CI, Netlify
EncryptionThe connection is encrypted between Gitlab and CloudflareNo encryption provided for custom domain
Server Response TimeSlowFast
improvement in Google Page Speed test for more than 20 points
Netlify CMS IntegrationNot available yetAvailable

Cloudflare #

I should thank Cloudflare for their free service for ultra fast CDN and free encryption certificate, caching etc. This increased the site speed from 60/100 to 95+/100.

Markdown #

Writing posts in Markdown language is very easy than using traditional HTML tags. It is in readable format so it’s easy to modify, when the changes needed. Whenever I make changes and push the commits to git repository, the CI automatically build the site to HTML pages. When the user opens up the website, they access the webpages which are built already. There’s no to and fro data data movement to load the pages.

Theme #

I use Next in this blog. Simple and look professional, yet modern. You will really know the customizations when start using it. I love it!

Ruda font is being used all over the place except the code blocks. I use the same font in my Android device as well.

Continuous Integration [aka] CI #

There would be a separate post needed, if I want to write about CI and the experiments that I have done, experiences that I have gained with each of the CI platform. As of now, I use Travis-CI and Netlify for building the site. I would write a separate post; the link will be available here when I am done.

Post Comments #

I am still in dilemma whether to use Disqus (most websites uses it, login using social networking is possible) or to use Gitment.

There’s no privacy guaranteed when using Disqus, Gitment is open sourced and privacy oriented. The problem is not all the users have github account to use Gitment comment system. I may add staticman, if I succeed.

Content Management System #

What is the success of Wordpress, the simple content management system. As of now, I have to depend on my personal computer, where the git is configured and I can locally run Hexo to see the output before publishing any post. Sometimes it is painful, If I have an online portal, where I can go and write posts and if it automatically publishes it, that’s going to be a welcome change.

Currently Netlify provides such option. When a new post created, Netlify creates pull request and builds the website temporarily. Once we feel the post is ready for publishing, it automatically merge the pull request and delete the temporary branch.

I have set it up already for this blog, but still not using it 100%, as I do some tweaks in the website. Netlify breaks if there are any commits passed during the draft to publish phase. Ideally I will move into it in some days.

Conclusion #

Thanks for reading the large post. There’s no technical details provided how I have setup each of the above mentioned services. I may write in more detailed way, when I get time. Feel free to comment/ask questions for clarifications.

Happy Writing!!!