I started running this blog in late 2017 having published in different places before and during that time I tried to write my own blogging-engine since I wasn’t satisfied with using WordPress anyways, having tried other CMS as well. What I wasn’t aware of that time was, that I neither needed yet another CMS nor something dynamic like WordPress since the only purpose my blog should have is displaying mainly text-based content. That’s it. So I tried to develop globs, an anagram for blogs, and made a list of features a blog-engine I would love to use should have: Markdown, LaTeX-support, RSS, CW/Spoiler-Warnings, focus on publishing text posts with occasionally embedded code and so on.
I’ve known jekyll before since I bumped into pages generated by jekyll quite often on GitHub, downloaded it yesterday, messed around a bit with its config and came to the conclusion that this may be the blog publishing system I was looking for.
it does what you tell it to do, no more, no less. It doesn’t try to outsmart users by making bold assumptions, nor does it burden them with needless complexity and configuration. Put simply, Jekyll gets out of your way and allows you to concentrate on what truly matters: your content. (quoted from jekylls readme)
My current set-up involves an nginx reverse proxy, jekyll being deployed via a private repository on my gogs instance and a post-receive webhook so each time I push new content to my gogs repo it’ll become available live within a few moments.
What I love about this is, that I do not need a webbrowser, not even a window manager, to write and publish posts on my blog, since a terminal with git and nano/vim/whatever installed is just enough to do so.