My static micro blog experiment is going better than expected. Generation is still around 25 seconds hot on my old laptop as like the last time. Well.. sneakily it’s closer to a semi–constant 5~10 seconds by tricking hugo into outputting empty base templates which “can” result in mostly reads by writing files that have changed (might make a blog post about this).

$ hugo
                   |  EN   
-------------------+-------
  Pages            | 1728  
  Paginator pages  |  662  
  Non-page files   |   13  
  Static files     |  430  
  Processed images |  572  
  Aliases          |   76  
  Sitemaps         |    1  
  Cleaned          |    0  

Total in 26010 ms

The temptation to bring in a js bundler is oh so very great. Deno bundle is obviously not designed to bundle js directly for the browser but you can get away with it up to a certain point.

I think my practical notes on xslt/xml are mostly complete and could work as a blog post this month. I got distracted last month trying out syncthing’s newest features… if I get around to editing those notes, they could work as a blog post at some point too.

rss and xslt are a cozy combination. Out of annoyance with my flaky Internet connection I’ve paginated the rss and json feeds. Know what? After exploring various feed formats, the underlying problem seems to be incentives in feed generation tooling correctness across language ecosystems and not formats? Invalid atom, rss, and json feeds are all over the net.

HTML compilation is fun to watch. Here’s what hugo’s --debug output for this blog looks like right now. Rendering takes about 25 seconds on an old laptop. The linearity is easy to see, but that’s the least of my problems ;-)

cgit is good. I’ve added a small note on using git maintenance with cgit.

I’ve returned from the depths of The Fediverse with a reaction hover short code. The RSS version of this post should replace that reaction with a gif image link.

I’ll play around with this stolen idea for a bit. Audio reactions might also be another idea worth exploring.

I finally “get” why most social media web designs use a narrow 2/3 base column layout. There’s a lot of practicality involved. For example, it’s easier to control media delivery and responsiveness with narrower dimensions.

I’m not too fond of narrow holy grail layouts. If time allows, I’ll add options for swapping between a few “cool” base layouts.

really need to suss out an offline mode for this thing once I find the time. There’s an isp or power company outage every 2~3 days or so. That’s a normal thing in The Bahamas btw.

If you’re curious as to why I’m mostly just pulling Bing Images, well… it’s one of the more broken feeds. The feed from web.dev is a good reference too, but Bing guarantees one image a day. This allows slowly coming to terms with my poorly written and inefficient templates.