Matthew Lang

I tried to get back to working on my theme for Micro.blog last night. I managed to hold out for a few minutes before tiredness and frustration kicked in.

I have a theme working locally with Hugo. I have created a theme on Micro.blog and have started uploading the individual templates, but it seems like such a chore, and there are some differences between my theme locally and what is on Micro.blog, in that my Hugo themes don’t always work on Micro.blog.

Is there a more effective way to do this?

There’s a difference between what to build and how to build. I hadn’t given it much thought until today, when I started to realise that I could improve the time it takes me to make an image template for a product of mine by automating the creation of the different classes and modules needed for each image template.

I spent an hour tonight working on a script that generates all the necessary code I needed. In addition to creating each code file, it also generated the absolute minimum amount of code required for each file to run successfully.

When building products, I’ve always prioritised what to build over how to make, but I need to start splitting my time more evenly between the two. Spending time on one can have some profound benefits for the other.

I’m pretty happy with the Hugo copy of my own Micro.blog theme I’ve been working on for the last couple of days. It will have a few customisation options for colour scheme and fonts.

I’ve been trying to clone the blank theme when creating this new theme in Micro.blog, but it appears to be using the Sumo theme from my current blog instead of pulling the blank theme from GitHub.

Hopefully by the weekend, I’ll have a working version for others to use.