There’s really good browser support for display-mode media queries and this article does a really good job of running through some of the use cases for your progressive web app.
I’m slapping my forehead—progressive web components is a perfect name for what I’ve been calling HTML web components. Why didn’t I think of that?
A Progressive Web Component is a native Custom Element designed in two layers: a base layer of HTML and CSS that renders immediately, without JavaScript, and an enhancement layer of JavaScript that adds reactivity, event handling, and more advanced templating.
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.
Progressive enhancement is about building something robust, that works everywhere, and then making it better where possible.
An excellent example of an HTML web component from Eric:
Extend HTML to do things automatically!
He layers on the functionality and styling, considering potential gotchas at every stage. This is resilient web design in action.
Here’s a handy little tool for generating CSS with :has() selectors in order to do quantity queries.
BeforeInstallPromptEvent vs. navigator.install
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.
Read the book I wrote about service workers. It’s all yours.