The problem# I wanted a web page to always show the latest version, but the page is a static page that is auto-regenerated when new data is available, and I did not want to complicate my setup by involving server-side logic in accomplishing that. This can be done manually by clicking the refresh...
The problem# The actual filename structure of my blog posts contains the publishing date while the actual publishing date used by Pelican is in the file in a line starting Date:. For example, this file is content/2025/1026-lint-blog-dates.md and contains the header line Date: 2025-10-26 02:00...
The problem# In a recent post, I wanted to include a large code block of a log. In order to not make the reader scroll past that long block, I put it in a footnote. But triple-backtick (```) syntax for code blocks doesn't work in Python Markdown footnotes: [^1]: Broken footnote, do not use:...
The problem# When writing blog posts, I like to use Markdown's reference-style links which let you avoid writing URLs inline and instead provide a short name and define it elsewhere in the document. I always put them at the end, which results in the bottom of the Markdown file looking like a...
The problem# I've recently been writing more series of blog posts or otherwise linking between posts using {filename} links. And also I've been adjusting the scheduling of my future planned blog posts, which involves changing the filename as my naming scheme includes the publication date in the...
The problem# In an RSS/Atom feed, relative links are a bad idea because it's unclear what they're relative to. There are ways to specify a base for them to be relative to, but since feed readers do not consistently respect those mechanisms, it's safer to just always use absolute URLs in feeds. And...
As I mentioned a long time ago I am using Pelican for publishing my blog. I recently did an upgrade which broke the syntax highlighting, and I thought I should take a short time to explain how to fix it because I couldn't find a solution anywhere. The problem: it used to be the case that you...
Lately I moved my blog to Pelican. I really like how simple and flexible it is. So in this post I'd like to highlight one particular aspect of my Pelican's workflow: how to setup a Debian-based environment to build your Pelican's website, and how to leverage Pelican's Makefile to transparently use...
This blog is powered by Pelican and hosted through GitHub using GitHub Pages. In this post I'll describe the workflow I use when deploying new posts. For those of you not familiar with these technologies, Pelican is a static site generator - meaning you can write your content in a format such as...
Today I switched from WordPress.com to Pelican and GitHub Pages. First off, let me say: almost all URLs that were previously working should still work. Only the feed URLs are broken, and this is not something I can fix. If you were following my blog via a feed reader, you should update to the new...
Pelican has built-in support for GitHub Pages. However, I noticed that the ghp-import command might screw up the commit log if your GitHub Pages and your Pelican source code share the same branch name. According to the document of GitHub Pages, the user pages should be committed to master branch...
Nach langer Zeit der Abstinenz, unter anderem ausgelöst durch den Plattentod des Blog-Hosts, habe ich beschlossen mal wieder ein wenig zu bloggen. Wie sich das gehört habe ich also als erstes einmal den kompletten Blog umgebaut. Was hat sich geändert? Das Aussehen! Und mit dem Aussehen auch die...