Colophon

I made my first website when I was a teenager in the mid '90s, producing artisanal hand-written HTML in Notepad.exe. Like probably everyone at the time, I learned by viewing the source of other sites, which was actually readable back then. Once done I'd FTP everything to my ISP over my 28.8k Modem Blaster (Creative Labs, makers of the Sound Blaster audio cards also made these!) then sit back and tap F5 to watch the hit counter go up while the rest of the animated gifs and midi file loaded.

In the years between those heady days and now I guess I didn't have much time for fiddling around like that but I was lucky enough to work in some places that had strong internal blogging cultures, where writing was the primary way to share ideas and get things done.

In 2025 I decided to slack off take a sabbatical, so I had some time on my hands and nowhere else to write. I dusted off one of the many unused domains and set up an old school blog.

The content is just whatever I'm tinkering with or thinking about at the time. It's kind of my list of things and ideas I find interesting enough to write about, and my way of remembering things I read, rather than stashing them somewhere they never get read again. I'm trying to keep my standards low and just play.

How it's made

I started out how I started out, with hand-written1 HTML and CSS. I sort of had this idea for a long time that the hypertext markup language was, after all, made for exactly this, so why have some other abstraction to that?

But over the course of a few months I guess I learnt from scratch why John Gruber invented Markdown. It's not hard to write HTML, but it's fiddly and it either interrupts the flow of writing, or is a pain to come back and add when you're done.

So now, I write each post as a Markdown file with two lines of front matter then run everything through a little build step that makes the page and updates the RSS feed. I know there are a lot of tools out there for this (Astro, etc) but my needs are pretty simple and these days it's not hard (and very fun) to make just what I needed.

So I guess my philosophy forked:

  • The site should be simple and lightweight. No framework, no client-side JavaScript, no tracking, no cookie banner, no newsletter dickover.
  • Writing should have as little friction as possible, so I do it more often.

I also wanted the RSS feed to read the same as the page. RSS 2.0 says that entity-encoded HTML is allowed but without a list of permitted elements, so every reader implements its own. To try and meet my goal, I use a pretty minimal set of HTML tags that I hope they all support, and convert relative URLs to absolute, as the RSS Best Practices Profile recommends. Otherwise it should be the same as a page on the web, and seems to work. If you read via RSS and find something broken, please let me know.

Hosting is simple too, I really didn't want to have things to update or manage, so it's hosted on Cloudflare Pages and deploys with a git push. The only server-side code is a function for my own that receives webmentions. I also run a separate Worker for sending them out.

Posts

Over time I've noticed posts come in three kinds: notes (short, most of them), quotes (someone else's words, with a little of mine) and essays (longer). I used to show what each post was and let you filter, but it didn't seem that useful, so I opted to simplify things and remove it.

Indieweb

The site is marked up with microformats, sends and receives webmentions, publishes a blogroll as OPML, and assumes the RSS feed is the main way people read. Feels just like 2003.

Contact

You can subscribe , follow or email me.

  1. Mostly. I used Claude Code when building the chrome of the site and to get all the microformats correct, but the posts I did by hand. ↩