Controlling Images

/images/_2adb4efa-13be-4e64-8bd0-c642cf49363b.jpeg

I’m trying to keep the web system simple. At the moment, I can write one of these updates in about 3 minutes. It’s a great way to summarize my progress and think through next steps, then push them out to the public stream for anyone who might be following along.

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

But with more options I’ll have to start thinking harder about the updates and end up making fewer of them. More features = more friction. So I’m planning to put all my big effort into the overall look of the site, but each article will have to pick between just a few different layout options. And images are one area I have to be particularly careful about.

I’ve implemented a simple mechanism for indicating what I want right in the Obsidian link. With page links, I can specify a friendly text string to show so the site won’t get visually cluttered with long, hideous URLs, but that friendly name is ignored if you add it to an image link, so I’m just commandeering that friendly name.

Ultimately, I’m going to parse the string as a list, so I can do things like “thumb, left” or “paragraph, center”, which will be assigned as CSS classes to the image and I’ll be able to invoke any class that I’ve bothered to define in the site style guide, but for now I support just two options: nothing, which results in a full-sized image; and “thumb”, which will show the image in thumbnail size. I’ll implement the rest once I figure out how Nikola turns link text into HTML.

And if the


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