Fifteen years ago today, I published my first blog post and I wanted to mark the occasion with - you guessed it! - a blog post. I didn't really have a strong sense of what I wanted to say but, anniversaries being a chance to reminisce, I found myself revisiting what I've written over the years.
Fifteen years ago today, I started blogging
Constitutions are a lot more malleable than I would like
It always amazes me to think that Prohibition in the U.S. was implemented via a Constitutional amendment, as was its repeal.
In my head I think of a Constitution as a country's legal axioms - the foundation of its law system. From this perspective it makes sense that the prohibition of alcohol, having no Constitutional basis, had to be passed by adding another axiom. And when people realized that this was just a bad idea, it makes sense that getting rid of it required adding yet another axiom. It's funny, when you think about it, like a big legal "oops!" that you can't erase.
It turns out other people have done most of the work for displaying webmentions in #Eleventy
Webmentions are the way people have conversations on the Indieweb, but integrating them - or, indeed, any kind of dynamic content - into a static site can be a little tricky. Luckily, many people have run into this issue before and so there wasn't much for me to do but steal.
#TypeScript enums are kind of weird
An #indieweb aware approach to unfurling URLs in @eleven_ty
As a participant in the IndieWeb, I publish my share of likes, replies, reposts, and bookmarks. These posts all have one thing in common - they refer to another, external URL and only make sense in the context of that URL.
This being the case, it's nice to give my readers (and myself) some sense of what I'm referring to when I post that content. The process of scraping metadata from URLs for display purposes is called "URL unfurling" and implementing it efficiently on an Eleventy based website is not entirely trivial, especially when you're trying to save your Netlify build minutes, so it's worth sharing what I've learned.
As you probably already know, Eleventy is a static site generator. It generates output HTML files from input template files. In the simplest case, one HTML file is generated for each (non-layout) input template.
After some consideration I've decided to remove the articles from my "Posts" feed and rename it to "Notes". It now contains just my notes and photos (and videos if I ever start posting those). As before, my articles are available in my "Blog" feed.
Initially, my reason for mixing articles, notes and photos into one "posts" feed was that I suspected at least some of my readers would want a feed just for "original content", and the "posts" feed provided that. I still think this is true, but some other insights have led me to reconsider the approach.
Classifying your #indieweb posts with @eleven_ty
As mentioned previously, I recently converted my website over to Eleventy. I'm an IndieWeb participant and, moreover, my website is fairly complex so I ended up writing (or, in some cases, pilfering) a fair amount of code to make it all work together in an acceptable manner. I thought I would document the process via a series of blog posts in case anyone else finds it of value.
Making the switch from Pelican to @eleven_ty
After roughly five years, I've finally decided to switch my blog over from Pelican to Eleventy. I'd be lying if I said that I wasn't at least partially swayed by the fact that all the cool kids seemed to be doing it but, with that in mind, I do have some (hopefully) legitimate reasons for making the switch.
The ins and outs of owning your bookmarks on the #indieweb
From a technical standpoint, there's virtually no difference between these kinds of posts; they're all permalinked h-entries which house another, usually external, URL and which often contain no other content beyond that link. They differ solely in the microformat which annotates the link, indicating the intent of the post.