Archives for 2022/03 (Lifestream)

I'm not religious, but I occasionally think that for some people, their purpose in life is to be a cautionary tale, and that makes me sad.

Pagination in Eleventy is bit strange. Out of the box, Eleventy comes with support for something the developers call "pagination", but it might not be the sort of pagination you're used to.

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.

The feature known as pagination in Eleventy is basically a way of getting around that limitation, allowing you to generate multiple output files from one template file. If you squint, you can see how this maps to the traditional idea of pagination (i.e. we want to break down a long list of items into smaller sized pages, writing only one template for the page) and although this is, indeed, a common way to use pagination in Eleventy, it turns out that the feature is much more generic than you might think - and, paradoxically, less useful than you might think.

Read more »

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.

Read more »

Evelyn calls him "Laser Jesus"

Recent interactions on Twitter have led me to clarify the purpose of all my feeds with descriptions, so hopefully people will have a better idea of what they are in for :-)

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.

None of this is intended to be an Eleventy tutorial and you'll get the most from these posts if you already know something about how Eleventy works.

Read more »

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.

Pelican bills itself as a static site generator, and so it is, but one that focuses more on traditional, single user blogs. Pelican can, of course, be used as a CMS, and you can certainly use it to create arbitrary, standalone pages and websites, but the features in support of this usage seem more bolted on than organic. There are certain assumptions built into Pelican that stem from its original purpose as a blogging engine that are occasionally irritating to circumvent.

Read more »

Like many Indieweb participants, I post bookmarks, likes and reposts to my website.

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.

And intent make all the difference here. A like is supposed to convey that the author actually enjoys or appreciates the content to which the post is linking. A repost is supposed to convey that the author wishes, for some reason, to share that content on their own feed. A bookmark is supposed to convey that the author...ugh...err...

Read more »

More generally, is there any advantage to hosting your albums on an #indieweb enabled website, as opposed to a dedicated application, assuming the app was under your control (in other words you still own your data)?

So what does the #indieweb use for storing photos/albums? I run a micropub media server on a remote machine, storing the photos on disk. Any advantage to switching to the cloud (a bucket, for example)?