My customizations
This page lists customizations I’ve done to my Nikola installation, or want to do in the future. Listed in reverse timewise order.
Open
Customizations that I intend to do in the future.
RSS feeds
Have not received and love or care up to now. I doubt they’ll work.
RSS feeds and languages
The “what is an RSS feed” explanation is in English even if the feed itself only has German material only.
RSS feeds not separated by language
There should be at least an RSS feed of everything, including both English and German posts.
Publish automation
Each publish operation writes a state_data.json
file with a “last
deploy timestamp”. I would like to check that in automatically via
git
as (a late) part of the publish operation.
Tag translations
The English tag tales and the German Dönekes are translations of each other, but the software does not understand that yet.
De - <div>
I am not a friend of the <div>
HTML tag. So I would like to run
my blog without using it. - This is partially complete, there are
far fewer <div>
s here than most pages use; certainly fewer
than plain Nikola uses.
Jupyter notebook integration
It somehow works, but I’m not yet pleased with the formatting.
Cleanup
There is a lot of cruft here that’s leftover from where it came from. That should be cleaned up.
Done
Customizations that are active in the version you are reading.
git repo
Provide the git repo with everything for people to clone somewhere public.
This would also nicely double as a back-up facility.
Other languages
The navigation to other language versions of the same post (or other material) is ugly. It currently says
Languages: Deutsch
where “Deutsch” is a link to the German version of the post.
- It should be “Other languages in which the article is available.” or something.
- The link does not lead you to a language, but just to another version of the article.
- It is always plural “Languages”, not “Language” if there’s only one (and there is only at most one in my case).
- Looking at the HTML that’s generated, the link is outside the
<nav>
block that exists anyway, but instead in a mere<div>
. (I personally do not like<div>
s and avoid them whenever more specific elements exist.) - As I’m offering two languages at most, the UI can be quite unobstrusive.
Descript
I don’t think a normal blog needs any JavaScript to function. This one does not have any JavaScript, I think - certainly not in the main blog pages.