Yeah, I know, I was away for a while and some things broke.
In apology, take this: breaks fixes, and some improvements!
No really, these might actually be useful to anyone reading this, and not just me.
Well, some of them.
If you’ve clicked on this post itself, you’ll notice there’s a sound file at the top.
That’s because if you click it, or hit the P key, you’ll hear… me, reading this!
I’m working on adding this to old posts one by one, so you might see that popping up eventually.
But, partially for accessibility, and partially just to make these sort of ramblings easier to take in while only half paying attention or just doing something else entirely, I’m putting audio narration on every post here that I can.
By default, the Markdown renderer in Hugo, at this point in time, is Goldmark, a CommonMark compliant renderer.
CommonMark makes no provisions for manually specifying the width or height of an image.
There’s various extensions, like those for Pandoc, Kramdown, and GFM, but Goldmark doesn’t support those.
Google is getting a little cranky with the amount of CLS on some pages, especially on mobile, so it’s a good idea for me to start specifying sizes for most images.
How should I do this? By hacking it on as a feature that is in no way the intended use for anything involved.
If you remember when I first added the Medium Zoom library, I wasn’t using one of its features: the ability to load a larger image when the user clicks to zoom in, only when the user wants to zoom in.
However, I added this later, and in that, the method I used was to use a Hugo shortcode to include the image with proper attributes in the <img> tag.
Well as it turns out, I don’t need to do this.
Now, I can have that happen automatically with standard Markdown ![image links]().
Now I know I’ve talked about sitemap.xml before, but quick summary: that’s an XML file that has a list of every (public) URL on your site, to make it easier for crawlers to index your entire site since that list (or, map) lays it out. Well as an XML file, it can take XML style sheets, in a format called XSLT, short for XSL Transformations, short for eXtensible Stylesheet Language. Yes, it’s XML all the way down. But, if you’ve looked at my sitemap, you’ll see I’ve gone and done it. This is how.
Continue readingNow you might not see this too much since I plan to use the feature sparingly, categories and tags are both capable of sorting everything to a satisfactory level, but I’m using this thing that I just made to add extra little labels, which have a few cool uses.
Continue readingHas anyone noticed that I’ve been giving out URLs of the form tekdmn.me and not teknikaldomain.me?
Well, not only did I buy another domain that’s just a shorter version of this one, but it’s also, at the moment, the singular domain I have that’s 100% serverless.
How? Cloudflare, obviously.
For those unaware, when using Cloudflare to proxy your site, HTTP/2 support is usually on by default, and highly recommended, and you can also enable HTTP/3 too. But, for a while I thought that Cloudflare’s HTTP/2 would rob you of one of the really cool and touted features of HTTP/2: the server push. Well, as it turns out, that’s completely possible. Let’s dive in.
Continue readingSo here’s a short one for you: Do you like your temperatures expressed as °F, or °C?1
Well, there’s one fundamental issue with me writing like the way I have been. I can put, say, “I decreased temperatures by 20°F by cleaning the fans,” but if you’re a °C person, then you need to take a quick detour to convert that to units that you’re more familiar with. A common way to do this would be to notate that as “20°F (11.11 °C)”, which works, but I’m effectively stating myself twice, and hoping that I actually got my numbers right. Plus that opens up the possibility for writing °F (°C) one time, and °C (°F) another. So for basically no benefit except me getting to be proud of myself, let’s improve on that.
Continue readingYou all know how footnotes work here, right? A little superscript number at the end of a sentence, and a list of numbers at the very bottom of the article, usually little remarks or extra details that are useful but not worth interrupting the flow of the article as a whole (or references). There’s just one problem: the notes aren’t anywhere near their associated text, meaning if you do want to read them, you might need to do some bouncing back-and-forth to understand everything. Well, no more!
Continue reading