I understand the "starting point" part but I find the emphasis on "classless" interesting: you basically have to introduce a non-element selector as soon as you want make even the smallest layout change.
For anything beyond a single page document, I find something like matcha.css (https://matcha.mizu.sh, you can even pick your custom build on the same page) a practical starting point if you want to stay close to the elements.
Love the idea. It's really painful to cycle through every theme. Would be great to have a way to scroll through them directly, though... that would result in a bigger bundle, and I respect the hustle
Well, μ- is a million times bigger than p-. But last time I looked <https://news.ycombinator.com/item?id=45163827>, Pico CSS was 83 kB—nowhere near as small as that name would suggest, either.
I had a server-side app made for personal stuff, and pico.css drop-in is a pretty good baseline for an usable UI/page. Also visited some web hosts and their sites look perfectly serviceable with Bootstrap. I think it's a good way to railroad some of the more egregious things LLMs might do with regards to CSS.
Interesting. Having made websites I think "of course that makes sense!". As a practical matter, getting wanted page appearance can require adding a few classes. I've been guilty of class proliferation caused by perfectionistic tweaking of things to the last nanogram. Anymore I strive not to go there.
Not only that, but very few of them differentiate between a visited link and an unvisited one. I noticed this immediately when clicking through the list of themes and getting no visual indication of which ones I'd already looked at.
Eye opener. I think I looked through almost all of them and none got basic typography right such as less margin bottom beneath a heading (to the paragraph following it) than above.
I love classless CSS for rapid hand prototyping. LLMs are making this increasingly less necessary, but it's still great for creating tiny, performant CSS pages and some of the smaller ones can even be inlined in fewer bytes than it takes to make a 2nd round trip to the server to check if the asset has been updated. This is one of my secret weapons for creating web apps that load and render so fast you can feel the difference!
I understand the "starting point" part but I find the emphasis on "classless" interesting: you basically have to introduce a non-element selector as soon as you want make even the smallest layout change.
For anything beyond a single page document, I find something like matcha.css (https://matcha.mizu.sh, you can even pick your custom build on the same page) a practical starting point if you want to stay close to the elements.
Reminds me of this website for checking classless stylesheets.
https://dohliam.github.io/dropin-minimal-css/
I’m surprised how few of them support dark mode.
IMHO today dark mode support is part of reasonable defaults.
I think they're just really old and not supported by anyone.
It's honestly horrifying how many website just don't bother.
Like w3, the makers of the web accessibility checklist have a flash-bang of a website and noone appears to have cared enough to fix it
Wrote some css from scratch the other day, 7 lines and I was done, line 8 are 9 were dark mode support integrated with OS setting.
It's not that complex, there's some minimal frameworks here with 10kB of css code, it's ironic.
Love the idea. It's really painful to cycle through every theme. Would be great to have a way to scroll through them directly, though... that would result in a bigger bundle, and I respect the hustle
Here some quick thumbnails for all of them: https://i.imgur.com/KXjiYxO.png
Some really unexpected domain redirects for this one for some reason: https://www.cssbed.com/vanillacss
All the others are as you'd expect.
For me it is definitely Pico.css. Honorable mentions: simple.css, tacit, w3c-chocolate.
pico css has a newer fork: https://mucss.org
"Lightweight ~120 KB uncompressed"
We have different definitions of lightweight it seems like.
When I worked at the BBC in the late 90s / early 2000s the home page of any site - including images - couldn't be more than 70kb!
Well, μ- is a million times bigger than p-. But last time I looked <https://news.ycombinator.com/item?id=45163827>, Pico CSS was 83 kB—nowhere near as small as that name would suggest, either.
Brb, gotta go cough up some mucss
holiday.css for me, only 5kb to boot.
I like marx
I had a server-side app made for personal stuff, and pico.css drop-in is a pretty good baseline for an usable UI/page. Also visited some web hosts and their sites look perfectly serviceable with Bootstrap. I think it's a good way to railroad some of the more egregious things LLMs might do with regards to CSS.
Interesting. Having made websites I think "of course that makes sense!". As a practical matter, getting wanted page appearance can require adding a few classes. I've been guilty of class proliferation caused by perfectionistic tweaking of things to the last nanogram. Anymore I strive not to go there.
It's sad that most of these themes makes buttons not look like buttons.
Not only that, but very few of them differentiate between a visited link and an unvisited one. I noticed this immediately when clicking through the list of themes and getting no visual indication of which ones I'd already looked at.
Eye opener. I think I looked through almost all of them and none got basic typography right such as less margin bottom beneath a heading (to the paragraph following it) than above.
Many had zero left/right margins on mobile.
Overall terrible defaults.
[2019]
But might be due a revival on the shoulders of LLMs.
Correct terminology: https://en.wikipedia.org/wiki/Reset_style_sheet
What does resetting inconsistent browser behavior have to do with classless styling? Those two aren't the same.
I love classless CSS for rapid hand prototyping. LLMs are making this increasingly less necessary, but it's still great for creating tiny, performant CSS pages and some of the smaller ones can even be inlined in fewer bytes than it takes to make a 2nd round trip to the server to check if the asset has been updated. This is one of my secret weapons for creating web apps that load and render so fast you can feel the difference!