Finding the Framework

/images/_d011a834-7ebc-425d-9f40-3394249e9a6c.jpeg

As mentioned, I’m searching for a simpler way to manage my blog with minimal server-side requirements, easy posting workflow, and integration with both my phone and my usual note-talking infrastructure: Obsidian wiki. But lets get more specific.

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

My requirements are:

  • a static file system with no server back end other than the HTML server

  • no server side databases or code for me to maintain

  • no hackable entry points through which assholes can fuck up my life

  • like a lab diary for multiple concurrent projects, all advancing in parallel

  • content pulled from my existing markdown wiki system that I already use for my project notes

  • but only pulls specific posts that I explicitly mark for external sharing

  • the engine that turns markdown into html and pushes to the server must all be in Python so it will play nice with my existing tool infrastructure

  • supports one or more templating engines so I can prettify the site somewhat but will not be tempted into dynamic front-end coding

  • requires absolutely no manual interventions in the back end to handle new posts or projects

  • everything has to run comfortably on my ancient laptop

With those ambitions in mind, I spent some time today exploring the Nikola engine. I used it last year for a one-off experiment and I remember being pretty pleased at how well it delivered on all of those requirements. But sadly, I couldn’t even remember what it was called. (Thank you, geriatric memory degradation. :-) Anyway, after an hour of digging through old emails, I finally found it, and was able to begin the process of reloading my brain.

If you’re reading this on the site some day, then I must have eventually made enough progress to get something pushed to production, but that day was not this day. Today I was able to figure out a preliminary system for using page tags to control which articles get posted to which protect pages, and I got a bare-bones listing generated on my development machine. It’s ugly and it’s only 3 web pages, but it’s a start.


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