RSS Switchboard

/images/_a5727e29-52bb-467e-9f17-211c0655a82a.jpeg

I’ve mentioned that this will be my primary (and possibly only) presence on the web. But if it’s going to support all the different things I want to do, it’ll have to be pretty powerful. After implementing a basic “everything” feed, I sat down and sketched out what a more nuanced system might look like.

◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇◆◇

As with many aspects of this site, things get complicated because I like to have so many projects going at once, and in so many different fields and genres. I can’t expect people who follow my novels to be interested in my electronics projects, and neither of them are necessarily interested in my cartoons. Everyone who comes here comes for completely different reasons, so I want to be able to let each person pick and choose which parts they want to follow.

That means not just a feed for each project, but also a feed for each thematic tag. Maybe you don’t particularly care about any specific project, but you’re interested in seeing all my design sketches, or articles that touch on programming, regardless of which project they’re in.

So if I’ve got 20 projects and 30 thematic tags, that’s a lot of different feeds to manage. Fortunately, Hugo can do most of the heavy lifting for me, getting each article summarised into each of the relevant feeds. The problem, I think, will be making it easy for visitors to find the feed address they want.

My plan currently will be to have a drop-down menu called RSS Feeds next to the Projects menu. It will have at least a submenu for Projects and another for Themes, although there may be more later, if I discover other useful ways to categorize things. I’ll also put an RSS icon anywhere I show lists of tags or projects. Not obtrusive, but close at hand wherever you might decide you want it.

I’m not sure how many people still use RSS, but I’ve decided that I’d rather serve the few who actively come here consciously looking for a feed, than to push my stuff into social media and provide yet more content for the subconscious algorithmic exploitation of humanity’s collective attention span.


Read More


/images/_e1b23d38-68ca-45eb-bf1b-56bd12ad0ce3.jpeg

Obsidian-fu

Refactoring the shadowmaker has become a bigger headache than I had originally anticipated, but it’s for the long-term health of the system, so I’m sticking to my guns. This weekend added further drama when I finally stopped running away from frontmatter and embraced it for all my metadata. Sure, scattering #ch-command directives throughout the body of the notes was insane, but fixing it is going to mean more than just adding a few metadata fields. I may have to completely change the way I use Obsidian.

/images/_e42c8a8a-b127-431f-b414-425c5d17a2dd.jpeg

Ontology-2.0

While trying to integrate the many episodes of CaveTV into the site, I realized that the ontology was getting cramped. It needs to be revised to better distinguish between internal projects, external brand identities, multiple deliverables within a brand, and distinct showrooms.

What follows is the scheme we devised for what the abstractions are, how they should be tagged in Obsidian, and how the files will be managed within Hugo.

/images/_2ef531ec-bc45-46fe-841b-6864301fa06c.jpeg

Cutting The Monster Into Pieces

Now that I’ve identified a useable hosting candidate, my final test of their service will be to roll out a full implementation of the websmith deployment scheme. But in contemplating how I’m going to do that, I’ve realized that I may not have broken the project into distinct repos properly. So I’m going to figure it out by explaining it to the rubber duck. (Meaning you. :-)