New post: A refreshed look

This commit is contained in:
Luca Beltrame 2021-01-06 10:24:21 +01:00
parent 1a6152c540
commit fbaa838f44
Signed by: einar
GPG key ID: 4707F46E9EC72DEC

View file

@ -0,0 +1,55 @@
---
categories:
- General
- KDE
comments: true
date: 2021-01-06 00:30:09+01:00
disable_share: true
draft: false
omit_header_text: true
tags:
- general
- update
title: Refreshed look
toc: false
author: Einar
featured_image: "images/banner.jpg"
---
You might have noticed that the blog has a markedly different look than before. It has not only changed visually, but also under the hood. This (brief) post summarizes the reasons behind the change.
# Why?
Simply put, the previous solution was unmaintainable. "But," you might say, "it was a *static site generator*! How could it become unmaintainable?".
It can. You might recall I [moved from Wordpress to Jekyll about six years ago](https://www.dennogumi.org/2015/05/dynamically-static/). I chose the [Feeling Responsive](https://phlow.github.io/feeling-responsive/) theme at the time, but it did not do what I wanted it to do (including support of [Isso](https://posativ.org/isso) for hosted comments), and it was meant to be a landing page rather than a blog.
So, having probably indulged in something that altered my perceptions at the time (funny, because I neither drink nor smoke...), I forked the theme.
Yes. You read that right. I *forked* the theme. And to add the functionality I required, and in particular not to leave many broken links around I had to add several Jekyll plugins: some I even had to modify myself to make them behave properly.
Then...
# Then version updates happened
{{< imgthumb src="images/2021/frankenstein.jpg" size="200x" class="w-third center" >}}
Jekyll had several compatibiliby-breaking updates. I couldn't update my fork because it was far beyond my ability (I'm a scientist, not a designer nor a coder in the strict sense), and many plugins started falling apart. I had to hastily prepare a makeshift Docker image containing the exact versions of everything I had (Jekyll 2.5.x, even) and spend several hours trying to make it work correctly (that included using obsolete versions of Alpine Linux, for example).
In short, I made even a worse job than what Viktor von Frankenstein did. Unfortunately, I do not really want to be proud of that. The horrible contraption I built made even *writing* posts problematic, because the process would sometimes break.
It's good having a blog where not even the main author can write and expect things to be published, eh?
# A solution?
More recently, I've been reading about [Hugo](https://gohugo.io/), a rather fast static site generator which also happens [to be packaged for openSUSE](https://software.opensuse.org/package/hugo). In particular I found the approach to theming better than Jekyll, because you can just override parts of a theme should you require it, instead of forking a whole theme and hope for the best.
Thus, I used the [Ananke theme](https://github.com/theNewDynamic/gohugo-theme-ananke) with some extra additions (documented in the [git repository](https://git.dennogumi.org/websites/dennogumi-new)). Importing things was pretty painless. The CSS wasn't, and I'm sure there are still loads of broken things, but at least I'm moving forward. Please leave a comment if you find anything broken, thanks!
{{< imgthumb src="images/2021/merlin.jpg" size="700x" caption="Conquests of Camelot: The Search for the Grail - © 1989 Sierra On-Line" >}}
Hopefully I can blog a little more than just making an update and disappearing again (not that I've disappeared: I've been fairly active doing packaging work in openSUSE). But again, to quote the words of Merlin, "it is a secret only known to the ancient gods and me."