What you see really is what you get. I like this style!
If we were to follow Jiro’s and his apprentices’ journeys and imagine web development the same way then would we ask of our junior developers to spend the first year of their career only on HTML. No CSS. No JavaScript. No frameworks. Only HTML. Only once HTML has been mastered do we move onto CSS. And only once that has been mastered do we move onto JavaScript.
And by LLMS I mean: (L)ots of (L)ittle ht(M)l page(S).
I really like this approach: using separate pages instead of in-page interactions. I remember Simon talking about how great this works, and that was a few years back, before we had view transitions.
I build separate, small HTML pages for each “interaction” I want, then I let CSS transitions take over and I get something that feels better than its JS counterpart for way less work.
This is very nice HTML web component by Miriam, progressively enhancing an ordered list of audio elements.
If you like the prospect of an old man ranting at clouds, this is for you.
Having fun with view transitions and scroll-driven animations.
Try writing your HTML in HTML, your CSS in CSS, and your JavaScript in JavaScript.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
HTML web components for augmenting date inputs.
Going back to school in Amsterdam.