Messing around with a statically generated site can easily lead into a web/browser spec rabbit hole. And.. that’s when I remember exactly why everything ends up written outside the browser’s framework into a js framework. I think Firefox is still the only browser that allows easily setting image fallback styling completely with just CSS?

Hyperscript Tagged Markup (htm) is pretty good. It uses tagged templates.

The Enhance Framework looks compelling. Personally, web components and more particularly the shadow DOM are not very appealing but… the template structure looks clean for drawing up components/layouts super fast while still being primitive enough to not lose transposability between different environments.

It seems like there’s an uptick in discussions online around web components but maybe that’s just the typical developer marketing/advocating. Web components have been around for a bit.

I’ve since realized that Hugo’s architecture provides a variety of template optimization strategies. Hugo builds pages concurrently, so it might be hard to see on a modern device but before partialCaches or module mount trickery — there’s still the implicit complexity of the output/lookup model.

Generally the complexity cost of the default output formats are: page > term > taxonomy > section > home. Keeping expensive calls inside a section and/or a home template is usually optimal. i/o and maybe memory should be the only problems with lots of pages.