How to progressively enhance a nav menu | Go Make Things
A lot of folks assume that progressive enhancement means having to write the same code twice, but often, it can be as simple as extending the pattern you already have once the JS loads.
What’s important is that you test it with real users… and stop using hover menus.
Strong agree!
A lot of folks assume that progressive enhancement means having to write the same code twice, but often, it can be as simple as extending the pattern you already have once the JS loads.
One way of implementing the growing/shrinking navigation pattern—an alternative to just shoving everything behind a hamburger icon.
I think the situation that Remy outlines here is quite common (in client-rehydrated server-rendered pages), but what’s less common is Remy’s questioning and iteration.
So I now have a simple rule of thumb: if there’s an onClick, there’s got to be an anchor around the component.
I had a great time chatting with Lea and Emily about service workers on this episode of their podcast—they’re such great hosts!
Here’s the huffduffed audio.
I like this declarative approach to associating JavaScript behaviours with HTML elements.
I never would’ve known about the `display-mode` media feature if I hadn’t been writing about it.
Having fun with view transitions and scroll-driven animations.
A defensive enhancement to avoid losing everything you just typed into a textarea.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
Gotta keep ‘em separated.