New Landing Page

/images/NewLayout.jpg

Today started with a bit of AI exploration looking at a bunch of layout concepts for the look of the new website’s landing page. Lots of weird and head-scratching proposals were made, but this one has some stickiness to it. I had been thinking that the featured article would be on the left, and the smaller “other” article boxes would be on the right, but now I’m digging this proposal, with the feature right in the middle of an expanded banner section.

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

The imagery of the banner seems a little “alternative medicine” for my tastes, but conceptually, this feels like something I can work with. Assuming I can make it work within the HTML template engine I’m using.


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. :-)