The Initial Blot Setup
Setting up this blog with Blot was pretty straightforward.
It all started as an experiment. But now, it’s not. It’s something permanent1. In less than a day, everything was set up and running. From the setup of the domain name (with GoDaddy) to having an actual site available for browsing. This is the very short story behind setting up the Numeric Citizen I/O website with Blot.
My interest in Blot came from the desire to have better control over the visual appearance of my microblog, which is hosted on Micro.blog. Micro.blog supports some customization but it’s too demanding as you have to have some knowledge of HTML, CSS and Hugo templates inner working. Another goal was to own my content.
Blot is a nice solution to my objectives: owning the content, easy visual styling, and easy publishing. Blot allows me to keep using my current applications like Craft for initial post writing Ulysses on the Mac, which supports Markdown files for editing. I had to select a GIT client to complete my workflow for publishing blog posts.
Opening my account on Blot was super easy. Before going further with any of the Blot settings, configuring my GIT client was mandatory. Cloning the Blot repo on my machine was quick and easy, too. Any non-fixable issues at this stage would have jeopardized the whole initiative.
Next up: setting up analytics, page structure, support for commenting blog posts, and closing a link format. All of this was dead simple to set up. But I wasn’t done yet. The next step was to select a visual theme. I wasn’t satisfied with the available themes, so I asked for support for help as I knew there were other themes available. After describing what I was looking for, the guy behind Blot agreed to bring back one of the decommissioned themes (for an unknown reason). In fact, it was the previously available default one. This closed the loop. I’m a happy camper now. I like this theme because it gives this blog a “scientific paper” look, and I love it; it aligns with the blog’s purposes.
-
As I’m porting this content to my Micro.blog hosted metablog, I recognize that nothing is permanent. ↩︎