
Responsive Components for Layouts You'll Never See
Swap a card's viewport media query for a container query the host establishes, find the breakpoints its content needs, and keep user preferences and product intent in the mechanisms that own them.

Swap a card's viewport media query for a container query the host establishes, find the breakpoints its content needs, and keep user preferences and product intent in the mechanisms that own them.

A practical way to evaluate a frontend technology as a long-term commitment, from how much of your app it takes over to what replacing it would cost, with my own decision to build on Lit as the example.

The two best-known fixes for a slow list solve different problems and cost you different things. Measure which cost you're actually paying, then keep the DOM with content-visibility: auto or drop it with a virtualizer and rebuild the behaviors that disappear with it.

Build an FAQ that stays findable when it's collapsed, learn which hiding technique to pick by who should still reach the content, and let <details name> and hidden="until-found" hand discovery back to the browser.

Build a smart badge whose foreground, border, and tonal dot derive from one accent, and learn which color decisions CSS can own with color-mix(), relative color syntax, light-dark(), and contrast-color(), and which still belong to your design system.