Project WebSmith is about more than just creating a website. It’s about creating a “thought-sharing” extension to the system I use for keeping my personal notes. Whether it’s ideas for a project, progress notes, book reviews, thoughts about social issues, whatever. I keep all of that in one place. And now I want to be able to share selected entries automatically. So the project name “websmith,” isn’t only about the worldwide web - or also refers to my own personal web of ideas, projects, and communications. (I’ll leave the origin of the “smith” part as an exercise for the reader. :-)
The primary interface for this system is my personal wiki, which I’ve been using in one form or another for almost 20 years. For the last 5, it has resided in Obsidian, which I access almost exclusively through my Android phone, although I also use vim when I’m working on a computer that has a keyboard.
The public-facing side of all this is being driven by Hugo, which takes any notes I’ve flagged for public consumption and builds my new website from them. If you’re reading this and you aren’t me, chances are high that you’re viewing the results of that pipeline now. :-)
This project stream will be about my adventures shoe-horning Hugo into my existing Obsidian workflow.
The more tech you allow into your life, the more time you’ll spend fixing tech.
Sigh. Yesterday I discovered that there’s a crucial component in this whiz-bang site management system that I had not considered. How did I discover it? Because it failed. So now progress on all other fronts has to take a back seat while I figure out how to either repair or replace it.
And the tech in question? A tiny Raspberry Pi.
It’s funny how hard it can be to defuse old habits. Historically, my approach to writing code has always been to plan out a good architecture and then implement the framework first, knowing that any time spent building a decent infrastructure first can pay off enormously over the life of the project. But as part of my new policy of leaning into my distractible attention span, I’m embracing a more “rapid prototyping” workflow. Unfortunately, somebody forgot to inform my subconscious about the new plan.
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.