About and Gallery

/images/_21f95986-b39f-47b3-9a66-b00a05b30ec8.jpeg

A couple of powerful features added today that will eventually let me do some cool stuff, but none of those actual cool things added yet.

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

Cool Thing #1: Static Pages

I can now generate static pages (About Me, Privacy Policy, etc) by tagging an Obsidian page with ch-page but not assigning a project tag. (Clearly if a page isn’t about a project, it must be about the site as a whole, right?)

Cool Thing #2: Project Galleries

I want to add an image gallery for each project, but only for images that are substantive, like product visualizations, design sketches, circuit diagrams, etc. (Nobody wants to browse a gallery polluted with amusing cartoons and other purely decorative nonsense.) But to make that happen, I first had to build a database of metadata from the images. The shadowmaker now extracts a bunch of useful info from the image description, including a ch-vis tag to indicate that the image is a visualization.

Armed with that, I’m now able to create a gallery for each project, which gives an interesting way to quickly skim a project history and maybe dive into anything that catches your eye. But full disclosure: I have the ability, yes, but I have not yet implemented these actual galleries. Hopefully coming soon.


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