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.

Hugo is a gateway for discovering neat golang libraries. Version 0.104.0 introduced a color extraction method that has lots of use–cases. An easy one is to generate basic image gradient placeholders. The browser has its own deferred/lazy loading logic so fancy image gradients (on a static site) require only a few lines of pre–generated CSS styles.

Reverse pagination is a counter–intuitive strategy for attempting to make links immutable/cacheable and bookmark friendly across older pages. I searched for a visual explanation (difficult to explain concisely) and eventually arrived at an old article on paging apis. Reverse pagination has its gotchas, but then again pagination itself is one big gotcha.. :-) Well, it depends on the use case really.

It’s kinda neat how CSS animation rules are sort of simple in their construction. imo, rules could be made even simpler if the animation-delay property also allowed delays between iterations/intervals instead of at the start only. Interval delays could allow for writing drastically less key frame rules.

text-animation[hang] {
  animation: tilt-rightward 1.3s infinite, tilt-leftward 1.8s infinite;
}

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.

If you think about it, the HTML <abbr> tag is not that well thought out. Or rather, inconsistent interpretations of the title attribute on different displays limits <abbr> usefulness.

Sure, conditional media types allow auto expanding the title on touch or print displays.

But many semantic elements have similar quirks that are only noticeable with a good cross browser/display testing suite, which no one has btw.

Surprising quirky behaviour + real world “get it done now” business constraints = everything’s a <div> and/or a <span>.

Blade CLI is a nice find. I saw a past iteration of this a while back in nsrosenqvist/blade-cli. Basically, it’s a cli for kinda rendering blade templates. Don’t ask why…

name: {{ $name }}
type: {{ $type }}

blade render data.yaml --name="name" --type="type"

Htmx is a nice library to know about that makes frontend = backend. Include strategic js (htmx.js) to not write any more js and compose an interactive website/application in HTML only. Use your favorite back end to create routes that return partial HTML that is swapped in on event triggers (transclusion).

Ngl, most of the fastest web spas I’ve seen were using nuxt.js. Performant react web applications are rare… But honestly, the usability of the web overall is in the gutter. I’ve spent these last few days watching people frustrate themselves over broken web application forms (for banks especially).