Tagged blogging

My blog is based around Eleventy, which means I write my entries in plain text, using Markdown and YAML front matter, a combo which I'm sure is familiar to most users of static site generators.

I also participate in the IndieWeb, which means I post many different kinds of content other than your standard blog posts - notes, likes, photos, etc.

I find it useful to divide my content in two main types: original content, where the focus is on my own published material, and derivative content, which only makes sense in the context of another, external URL.

Read more »

About five years ago, in early 2019, I stumbled upon the IndieWeb, a movement and community dedicated to modernizing the personal website. I quickly became enamoured with its ideas and spent the next year revamping my website and blog to make it more compliant with their standards.

I've written about the IndieWeb before but if you're just tuning in, there are several dimensions to it:

I pretty much went whole hog here; my website and publishing workflow supports all of the above, and link previews to boot. Not particularly well, mind you, but that's a different conversation.

Read more »

My blog is 16 years old. I've rotated through several blogging engines in that time (Bloxsom, YAWT 1.0/2.0, Pelican and finally Eleventy) but they all have one thing in common: they all process blog entries stored as plain text files.

The fact that all my blog entries are stored as plain text files on my computer is, I believe, one of the main reasons my blog has lasted this long. Text files are trivial to back up. Text files don't really crash and rarely get corrupted. Text files are readable and writable on any computer manufactured since the 1980's - hell, the 1960's if I let punch cards into this conversation. When you contrast this simple durability with, for example, a MySQL data store (used by several blogging engines, including one of the most popular ones, WordPress), with all of its attendant version compatibility and data corruption issues, the superiority of plain text becomes undeniable if you're trying to write something that lasts.

Read more »

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.

It's definitely a mixed bag. The tone and content vary quite a bit. For this reason, when people ask me what this blog is "about", I don't usually have a ready answer, and this sometimes catches them off guard because common wisdom states that blogs typically have themes. People will manage a cooking blog, for example, or a programming blog, or a reading blog. Among other things, it's a way to collect followers - people seem to place greater trust in a blog when it focuses on one subject.

Read more »

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.

Read more »

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 »

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 »

If you're a programmer of a certain age, you've either read or know about Design Patterns, a book on software architecture popular in the 90s and early 2000's. The book was sort of like a repository of TV tropes for the Object Oriented Programming (OOP) world in that it provided a convenient vocabulary for describing what were usually eminently recognizable software engineering techniques that nonetheless often lacked punchy, easy to remember names.

Notably, the book was more descriptive than prescriptive. It described preexisting techniques that were already in use in the "wild", so to speak.

Read more »

Thinking of trying eleventy.  But I've put some much effort into my pelican setup.  Hrm.

My personal website is https://desmondrivet.com I have a blog on it and a kind of microblog as well. It's not wildly beautiful.  I write about whatever strikes my fancy, so I definitely wouldn't call it "cohesive".  But it's there and I use it and it's mine.

I don't know if I'd call it my favourite, but I use @getpelican, @NetlifyCMS and @CircleCI.  Mostly because I'm semi-familiar with Python and Jinja2, CircleCI was faster than TravisCI, and Netlify is just easy.

I wonder about combining static site generators and photo galleries.  I know it's a thing, and yet it feels a bit off, especially when you have 10GB of photos.

I attended my first IndieWebCamp session last week, on the subject of "gardens and streams", otherwise known as wikis and blogs. Given the current global situation, the entire thing was remote; I participated via Zoom. It was fun! I'm glad I got to meet everyone.

Wikis, and how they differ from blogs, is a topic that interests me. You may not know it, but my domain sports a wiki, powered by MoinMoin. I mostly use it to store technical notes and recipes.

(Edited 2024/12/25: I no longer use MoinMoin, opting instead for an org-roam based digital garden, but the concepts are the same)

Read more »

I maintain website/blog at https://desmondrivet.com It's a statically generated site using @getpelican, hosted on @NetlifyCMS.  Updated semi-regularly and cross-posted to Twitter.

Jan-Lukas Else recently asked the Hacker News community why most of them don't have blogs, and published his thoughts on their answers to his own blog. The conversation was interesting and got me thinking about my own motivations for maintaining this site.

The first thing that stands out for me in the responses is the number of people who said that they quit blogging because they didn't have any readers. It was more than I expected. I don't think I fully realized how important readership was to some people in the technical community, probably because I think can safely say that it's not of great importance to me.

Read more »

Well, this is quite embarrassing.  Thank you for the information! Actually, my blog entries on my feed page did have p-names but I think I accidentally made them part of the e-content, and I suspect that's why they were not showing up. And, yes, my published date was embedded in my h-card for silly reasons that I won't get into. Anyway, I think (hope) I've fixed both issues if you want to try again.