Consider moving theme and/or blog engine

[StevenMaude]

Some thoughts:

• Hugo is faster than Pelican and seems to have overtook it in popularity and development activity, judging from a quick glance on GitHub.
• The theme used right now is Bootstrap 3 based and unlikely to be migrated to a newer version of Bootstrap as there isn't an active maintainer or team pushing development of this theme.
• Moving theme might require substantial changes, and therefore changing theme and blog engine might be sensible to do at the same time, to avoid having to repeat work in future.

TODO:

• [ ] Find a suitable Hugo blog theme.
• [ ] Investigate how much work might be needed to port across the source content.

[StevenMaude]

If sticking on Pelican for the time being, https://github.com/getpelican/pelican-themes/tree/master/Peli-Kiera doesn't look too bad and could be worth changing to, if there's not much work beyond switching themes. I'd remove the use of CDNs for CSS though.

[StevenMaude]

There's also Zola.

[StevenMaude]

Hugo looked OK; the issue was with trailing slashes. Hugo adds a trailing slash: this kind of makes sense from a filesystem perspective because its posts are within directories.

However, the way I have them configured currently is without a trailing slash. This makes sense:

• from the current filesystem perspective (as posts are all in one directory)
• from a semantic perspective (in my opinion) that the URL represents a specific resource and not a directory

If going with Hugo, and they never implement this feature (it's been mooted a couple of times in PRs but never finished), GitHub Pages does do an automatic 301 redirect of non-trailing slash to trailing slash, though needs testing. This isn't great though as it makes it slightly tricky if you want to revert to non-trailing slash.