Some thoughts—and kind words—prompted by my recent talk, In And Out Of Style.
A workshop on resilient CSS layouts
Oh, hell yes!
Do not hesitate—sign yourself up to this series of three online workshops by Miriam. This is the quickest to level up your working knowledge of the most powerful parts of CSS.
By the end of this you’re going to feel like Neo in that bit of The Matrix when he says “I know kung-fu!” …except kung-fu isn’t very useful for building resilient and maintainable websites, whereas modern CSS absolutely is.
I really like the idea of unifying some layout values in CSS. If you’ve got any feedback, please chip in!
This is very nice HTML web component by Miriam, progressively enhancing an ordered list of audio elements.
This is a great history of the idea of progressive enhancement:
It is an idea that has been lasting and enduring for two decades, and will continue.
When haters deny HTML’s status as a programming language, they’re showing they don’t understand what a language really is. Language is not instructing an interlocutor what to do in a way that leaves no room for other interpretations; it is better and richer than that. Like human language, HTML is conversational. It is remarkably adept at adapting to context. It can take a different shape on any machine, from a desktop browser or an e-reader screen to a mobile app or a screen reader for the blind (so long as that device is built to present hypertext).
Hell, yeah!
Ultimately, even as HTML has become the province of professionals, it cannot be gatekept. This is what makes so many programmers so anxious about the web, and sometimes pathetically desperate to maintain the all-too-real walls they’ve erected between software engineers and web developers.
Hell, yeeeeaaaaahhh!!!
What other programmers might say dismissively is something HTML lovers embrace: Anyone can do it. Whether we’re using complex frameworks or very simple tools, HTML’s promise is that we can build, make, code, and do anything we want.
How I switched to high-resolution maps on The Session without degrading performance.
Some buggy behaviour has been fixed in iOS 18 but now there’s a new bit of weirdness.
The Patterns Day conference, the workshop the day after, and an Indie Web Camp on the weekend.
I gave a short talk on a big topic.
It’s fine to require JavaScript for read/write functionality. But have you considered a read-only mode without JavaScript?