I’ve had it in progress a longgggg time. I mean, this blog post about what I’d learned about Hugo’s multilingual mode, which was prompted by my very adventures creating an Ido-language section of this site, was all the way back in March. More than once now I’ve been …
Last night I added a new statuses section to this site, where I’m gonna PESOS my status.lol posts back to here 🙂 Basically my plan is to compile a post each day with all the statuses, and post ’em as daily posts (rather than making a new post for every status which I think will flood my archives). This does mean not getting webmentions for individual statuses but oh well, lesser evils…
The daily status posts won’t appear on the front page’s recent activity feed, nor will they appear in the master RSS feed (but there is a dedicated “statuses” RSS feed you can subscribe to if you really want to see them in that format). The daily posts will appear in my archives though, under whatever month they were posted in. They won’t syndicate to Micro.blog, which already got all the individual status posts directly; nor will I post them to Mastodon.
Realistically, I’m expecting that the vast majority of people who see these statuses will see them on status.lol, or when they’ve been syndicated directly from there to Micro.blog and Mastodon. Copying them to my own site is more about my own desire for this site to serve as the canonical repository of all my shit – making sure I still have them even if sites shut down, or the statuses recede so far back in the timeline they’re non-findable. I don’t wanna count on any social media site retaining my posts forever, and even if most of these statuses aren’t really of long-term value, I wanna keep an archive 🙂
If you have a post with only one category, and choose between adding it to your post’s YAML metadata in one of the following ways:
categories:- Category Name
Those are not the same! According to Hugo, the first one is an array (of one item), and the second one is a string. So then if you later want to make a template where you range all posts’ categories, …
I just can’t stop tinkering 🙈 It’s been quiet on the blog for a few days, but I’ve added a bunch more wiki pages, including on the collapse of the USSR, the Inca Empire, the Transatlantic accent and Cyrillic. Also made it so that the wiki’s front page no longer lists EVERY wiki page (there are too many now!) and my RSS feeds no longer include wiki pages (except for, obviously, the wiki section feed) because TBH it was making me too self-conscious to publish new pages knowing they would appear in the RSS feed 😅
Over the last couple of days I’ve done a bit more site tinkering, and revamped my tag pages. Basically I wanted to be clearer about what the difference is between a tag and a category: a category is more like a channel, with posts on a similar theme but not all on the same subject, while a tag is more like a topic. So, the tag pages now (mostly) have a tag description at the top of the page (some of them seemed kind of self-explanatory or I couldn’t think of a good description though), and rather than being a paginated stream of all my content mixed together, they have shorter links grouped by content type (wiki pages, then blog posts, then link posts, then interactions). Many of them are like rudimentary wiki pages now 😛 And that’s why I wanted to make the change – to make it easier to link related content, and have kind of “stub wiki pages” for things I haven’t mustered up the energy to write full-length wiki pages for.
On the off-chance anyone is interested, I just published a big batch of languages-related pages from my Obsidian vault to my personal wiki. Most can be found if you start clicking links from the Romance languages page, but I also published one on the 2020 Scots Wikipedia crisis.
I’m not really sure the best way to bring stuff over from Obsidian to here – it has to be somewhat manual because I have to rewrite the internal links, and I also have a bunch of notes that I’m not really sure are worth making public (and some that I’m certain aren’t). But doing these big batches seems less than ideal, too 😅 I also get concerned that doing them might flood the feed reader of people who subscribe to one of my RSS feeds (the “master feed” or a category-specific feed will include new wiki pages). That’s sorta why I waited until now even though I wrote most of these pages a couple of weeks ago (so only a few will appear in the 20 latest entries of the feed – unless you subscribe to my “Languages” feed in which case you’ll get quite a few, but I figure that’s what you signed up for 😂). I don’t know, would it be better to exclude wiki pages from RSS feeds entirely, and just make a little note post like this when I add something new that might be interesting to others? But then I’d get self-conscious making note posts because I don’t wanna come across like I’m saying, “I GUARANTEE this new wiki page’ll be worth your time!” Something tells me I’m overthinking it, haha.
It’s been bugging me for a while that Vercel is generating incorrect “last modified” datetimes for my wiki pages on this site. What it seems to be doing is getting the last modified date only if it’s within the ten most recent commits. If the last modification was further back than that, it prints the last modified datetime of the tenth-most recent commit. From the docs it looks like Vercel is not even fetching git commit author dates (but commit SHAs and commit author logins, those it fetches…), so instead I guess it stores some cache that only goes back ten commits? I have no real clue, but because I don’t know how to fix this, I’ve commented out the part of my template that generated “last modified” text for my wiki pages. Better to display nothing than to have it display something that’s wrong for the vast majority of pages…
I mean… one way to fix this would be to build my site using GitLab’s CI/CD and just upload the built files to Vercel, instead of GitLab merely passing the source files along for Vercel to build. But ugh, what a hassle to change that all around 😩 Another strategy would be to manually set a “last modified” date in the front matter of pages I want to have one, and display that in preference to whatever git says. (Or even disable enableGitInfo entirely, if it’s just resulting in junk data.) That’d also be annoying, though. So, for the moment, I think just not displaying “last modified” dates’ll have to be the go.
I said the other day that I would figure out how to customise the syntax highlighting for the Nord theme, and now I have. If you want to grab the stylesheet for yourself, I’ve uploaded it as a snippet on GitLab. Some quick usage notes (which you’ll find in briefer form at the snippet page, too):