Post

en.wikipedia.org/wiki/Stockho...

I won't stand for this CSS slander. CSSlander? Wait. Stockholm Syndrome isn't what the 'SS' in 'CSS' stands for, is it? Oh dear.

I miss messing with CSS. Do you have any recommendations for resources for getting back into it as someone who hasn’t really touched it in ten years?

Nothing all-in-one, but I've found myself really inspired by @ishadeed.com's interactive posts (ishadeed.com/articles/) and pretty much anything @set.studio make (e.g. viewports.fyi). That inspiration translates into wanting to make my own beautiful stuff, then the rest is perseverance.

I haven’t bought a copy of this myself but I know @bell.bz knows his shit (he’s the founder of @set.studio), he’s recently released a CSS course that might be up your alley if you’re happy to throw some money at this itch. bsky.app/profile/bell...

Until about 2012 I really *knew* css, but then flexbox and grid happed, along with other new stuff. Life got busy. And I felt like I didn't know it any more. But I the last few years I feel like I'm back on it, I know flexbox now, and loving that it's caught up with SASS with nested selectors/rules.

Sadly I can’t use native nested CSS yet. I used it in a post and a reader got in touch to say the post looked weird to them. Debugged it and figured out the browser they’re using (Floorp, never heard of it before) was using an older Firefox-based renderer that didn’t support nested CSS 🫠

A couple of years ago, as a reaction to tailwind, I wrote a tiny js lib for extracting nested inline css from a html attribute. It was a lot of fun to make, the "un-nest" plugin is only 982 bytes. That experiment went nowhere, but point is that un-nesting css is quite easy github.com/samwillis/x-...

Should be able to run a PostCSS plugin over it for polyfill, surely? You can’t hold everything back for one obscure browser edge case…