Revolutionizing in the title of this post may be a bit strong, but I guess that is what you get when you ask ChatGPT to write you a “catchy” blog post title 😄.
Anyway, if you have followed my blog for a while (for the last 10 years or so) you know that I have been switching blog engines a couple of times:
- Moving to a New Blog Engine: Moved from WordPress to OctoPress/Jekyll (2013).
- Goodbye Jekyll, Welcome Hugo!: From Jekyll to Hugo (2018).
As you see from the above timeline it is around 5 years between each move. Seeing that it is now 2023 you may think I am switching blog engine again. Well, I am NOT switching engine.
NOTE: Having written the above (not switching), I had to, for sh*t and giggles, browse around to see what engines are out there in 2023 😄. I did, however, not find anything that took my liking.
What I am doing, though, is upgrading to the latest Hugo executable and, at the same time, switching the blog theme. This post is like a “Hello World” using the new theme and ensuring everything works.
Hugo is an open-source static site generator written in Go. It is designed to be fast and easy to use, and as I mentioned above, I switched to it in 2018. One of the significant benefits is that even though Hugo is written in Go, the executable with which you build your site(s) is entirely self-contained. In Jekyll, you must have Ruby and some other “stuff” installed on the machine where you build your site.
When I switched to Hugo, the most recent version was 0.46. The theme I used was the hyde-hyde theme, and as I had some specific ideas about how I wanted my blog to look, I customized the theme to a certain degree. To say I customized it makes it sound like I knew what I was doing (I didn’t), so the right way to describe it is that I hacked the theme. Below you’ll see how this was a mistake.
Anyway, my blog looked like I wanted it to, and everything worked fine.
That is until a couple of months later when I re-formatted my PC (I do it a couple of times a year) and re-installed Hugo. Suddenly I could not build my site anymore, and the errors pointed to some problems with the theme I was using.
Easily fixed, I thought. I will do a
git pull against the theme repository, and all should be good. Well, it wasn’t! After the
git pull the good thing was that I did not get any errors. The bad thing was that the site did not show, just an empty page 😒!
The problem I experienced was that when I reformatted my PC and reinstalled Hugo, I got the latest version of Hugo. The issue was that breaking changes were introduced between my original version (0.46) and the newest version. Amongst them were changes related to how templates were handled. That is why I originally got errors.
From a theme perspective, the author changed the theme to handle the breaking changes. That’s why I didn’t get any errors after pulling the latest theme version. The reason for the site not loading was due to the hacks I had done initially.
Realizing this, I decided that to “re-hack” the theme would be too much work, so I decided to go back to the old executable (0.46) and theme. That’s how it has been since late 2018/early 2019. I have kept the old executable and theme around and have been happy with the status quo. So what changed?
What made me realize I may have to drag my blog into the “modern world” was the purchase of the MacBook Pro M1.
Figure 1: MacBook Pro
As you know, the M1 silicone is based on the ARM64 architecture. Even though Hugo runs natively on the M1, there is no ARM64 version of Hugo 0.46. I found out this the hard way a month or so ago when I was in Seattle for the SQL PASS conference and wanted to do a blog post (I couldn’t).
This in itself was not that much of a “train smash”, but as I most likely will spend more time away from my home PC and still want to publish blog posts, I concluded I need to make some changes.
So, during the holiday, I upgraded to the latest Hugo version (0.109). Part of that change was also to change the theme.
Why did I want to change the theme? There was nothing wrong with the theme (apart from me having “hacked” around in it), but I had seen the theme Robin Moffat uses, where the theme supported banner/header images, and I quite liked that. That theme is the Story theme. Why I, in the end, didn’t go for it was that it is no longer actively maintained.
Apart from the Story theme, I also looked at the following themes:
I ended up using the Clean White theme, as it was the least complex theme and gave me almost everything I needed.
I will not go into details how I setup the theme - if I can do it then everyone else can as well 😄. What I will do however is to share some links:
Speaking of setup. Please let me know if you come across links that are not working etc.
If you have comments, questions etc., please comment on this post or ping me.
comments powered by Disqus