I've seen the blog question challenge going around recently among folks I follow and bacardi55 was kind enough to tag me to participate. So, without further delay, here we go!
Adam wrote up a post about everything on a site being a web page — posts included. He's absolutely write. I have some pages I think of on this site as being static ( about , uses , colophon et al) and these are often slash pages . But they aren't static .
If there's one thing I'm good at, it's torturing a metaphor. I grew up wrapped in quilts — my mom has made them for years (as a hobby and later, professionally). It's a passion, it's a patchwork assemblage of fabric — designs, patterns, mementos. They're handcrafted, require nigh-endless patience and the result is unique and irreplaceable.
Lately, one of the things I've most enjoyed doing on this site has been expanding on the facets of it that aren't strictly related to the blog. I've been working around the edges on filling out music, movie, TV and book related functionality.
I've written before about embedding music into my site and I've largely used Last.fm to do so. Their API is rather extensive, though it is showing its age — the default response format is XML, they've dropped artist images and have intermittently failed to return album art. ListenBrainz is great, but client support is still lacking. I've also tried charting Apple Music data from their (quite limited) API.
If I haven't made it clear enough recently, I love where the open web is heading and the indie web's part in it. This has grown out of the opportunity created by the ongoing fragmentation of the corporate social web and renewed interest in staking out personal spaces on the web. I've been blogging for a while and this is the longest period with which I've stuck with it and the most I've enjoyed it.
No, not that kind. I'm thinking of the indie web kind we're seeing lately. The kind that incorporates content from around the web that the creator of the site cares with and engages with. I find this to be complementary to the popular and well-explained POSSE concept. I've adopted this approach to populating numerous parts of my site, written using Eleventy, via frequent rebuilds.
The latest iteration of my website is built on Next.js, specifically Timothy Lin's wonderful Tailwind/Next.js starter blog..