Hey!
This site has been a bit of a talking point lately, eh?
I like it. I think it’s a good idea. I’m also a stickler for wording, so when I see ‘you might not need JS’, I read ‘you might not need JS’. A lot of these perhaps should be best left to JS, and the project itself doesn’t make any claim otherwise.
I recently had a bit of fun making a pure CSS content filter[1] which I ultimately decided should be done with JS, but the process of at least trying it was a bunch of fun, and taught me some things about CSS that I didn’t know.
Experiment, have fun, do things just because, but make sure you’re fully aware of the implications of making it public (which I think youmightnotneedjs.com did, but still took heat for it).
… especially using the radio/check buttons and :checked "hack"
There are documented issues with this, and we already know that it’s bad because we all call it the Checkbox Hack. Don’t use it :)
- csswizardry.com/2016/10/pure-css-content-filter