Don’t judge a book by its cover
Some neat CSS from Tess that’s a great example of progressive enhancement; these book covers look good in all browsers, but they look even better in some.
- Start with mostly static HTML.
- Progressively enhance the dynamic parts.
- Pick small, focused tools.
Some neat CSS from Tess that’s a great example of progressive enhancement; these book covers look good in all browsers, but they look even better in some.
This is depressing.
Great minds think alike! I have a very similar HTML web component on the front page of The Session called input-autosuggest.
There’s quite a crossover between resilience and longevity:
- Understand the requirements
- Keep scope small and fixed
- Reduce dependencies
- Produce static output
- Increase Quality Assurance
Framework monoculture is a psychology problem as much as a tech problem. When one approach becomes “how things are done,” we unconsciously defend it even when standards would give us a healthier, more interoperable ecosystem. Psychologists call this reflex System Justification.
The explains a lot about React-driven front-end development!
When a single toolset becomes the default, we don’t just prefer it, we build narratives that justify it. And that’s when a tool quietly becomes a gate or even a destructive force.
Here’s an HTML web component you can use if you’re participating in the origin trial for the Web Install API.
Reminding myself just how much you can do with CSS these days.
A redesign with modern CSS.
Having fun with view transitions and scroll-driven animations.
It’s almost as though humans prefer to use post-hoc justifications rather than being rational actors.