Looks like it’s time to rewrite the CSS of my main website for fast iteration and decoupling Hugo from PHP. I’ll still allow the generated files to move passively through the OPcache in case there’s a need for dynamicity. Hugo has pretty much deprecated all of my PHP hacks.

The dictionary and thesaurus are among my most used tools. They’re easy to install and use offline on any device — no search engine required. I just also realized that my most used offline tools are not in my blog post about programming without the Internet…

Hmm, this theme now coerces hugo into generating/bootstrapping authors from the site configuration file. The test result? @nobody. It might be an interesting pattern. Data mounting operates a bit strangely underneath the hood though, this issue (~2yrs) might be one to watch, but not too sure.

Time is generous. I don’t use/follow social media, so if this micro blog ever interfaces with a headless CMS there’ll be a constant deluge of posts.

Perhaps it might be an interesting experiment to document and wire in every API driven headless CMS available. It’s about time to put NixOS through its proper paces. How many heads can one fit onto this body or is it the other way round? It’s just an API after all.