Almost fully ported my existing website to #ikiwiki (switch over will likely happen within the next few days)
I plan to post directly to my existing RSS feed to let everyone know the new feed URL (give users a choice if they’d like to continue following 😉)
I’ve also enabled moderated comments and setup a “pending review” RSS for a hacky way to notify myself instead of needing a mail system. This setup has made me realize how much I miss having a simple web server (as opposed to purely static)
Almost done with the final tasks (functional web search, minor stying tweaks) before making the jump to #ikiwiki
I think having the option to write articles/wiki entries in both a webview or a terminal is a huge plus. Hopefully this gets me writing again more frequently :)
So, my recent review of #Teslagrad
(“Official” discussion thread: https://sociale.network/@oblomov/111471523707665307) has me facing an existential dilemma about my website.
Since its inception, I've endeavored to make it as lightweight as possible, or at least to maximize its “content to weight” ratio: until recently, posts were almost exclusively text-only, except for the sporadic self-hosted and often self-written vector graphic.
This isn't strictly necessary (#ikiwiki, which I currently use as static site builder, has the concept of “underlay” that can be used to fetch site contents from outside the repository), and would allow me to keep the repository lightweight (more so than the website at least). Tracking the images in the repository has the advantage of keeping everything together, and encourages for images the same “content to bytes” maximization that has driven my text usage.
Seems more up my alley as I plan to make my site into a more structured "info dump". A wiki lends itself better to that concept instead of a tradition "blog".
They also have clean instructions to get up-and-running via NearlyFreeSpeech
Shout out to @dabeaz for making "Practical Python" 1 available under a creative commons license. It works well for the hands on survey of programming languages course I'm #teaching this term. We only have 12 classroom hours to devote to #Python, but so far it's working better than my previous humble attempts based on "Dive into Python 3". No disrespect to the latter book, but somehow my translation into labs always seemed a bit disjointed. I don't yet know how the students are absorbing things, but to me the Practical Python based version seems to give a more coherent (and elegant) view of Python.
I am using the book/course unmodified, except that #ikiwiki automagically adds backlinks to where given sections are referenced in my add-on materials [2]. That shows the benefit of CC #licensing I guess.
Non tanto diaria: sui perché e percome degli aggiornamenti del Wok. Ovvero, perché dovrei scrivere di piú sul Wok, o almeno riportarvi tutto quello che metto su #Mastodon
Another annoying thing of #ikiwiki: tag links don't have a special class, so they can't be styled differently. Also all internal linking features don't offer a way to set the link title.
So, my main website is currently based on #ikiwiki. I like it because it's #plainText (no #database), I can work on it on my laptop using my favorite tools (#vim, #git), preview it locally, and then “deploy” it to a static set of HTML on the hosting machine. But there are a couple of things I do not like about my current setup. Chiefly: