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).

A CSS and HTML expert in the art is a marvel. Think less development and more engineering. The process of speedily assembling the minimum set of markup and style with maximum degrees of freedom. Like you know, a bassist can develop a new playing style, but there’s an engineering path where it’s perfected. OpenUI might end eternal widget development hell?

Can’t beat the hunch that once web components get widespread application there’ll be something like “micro apps”. Interoperable components between all js frameworks or something.

I know of four PHP static site generators.

1. Jigsaw: Laravel Blade templates. Source Code
2. Couscous: Twig templates. Source Code
3. Sculpin: Twig templates. Source Code
4. Spress: Twig templates. Source Code

The key advantage is obvious: dynamicity “technically” comes for free. Feedback/debugging loops “can” be made instantaneous, and scaling to a large output is probably not too difficult.

One downside is that corporate minded developers and consumers online will think you’re a noob for choosing PHP.