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.
sphars 12 hours ago [-]
Reminds me of this website for checking classless stylesheets.
IMHO today dark mode support is part of reasonable defaults.
etatester 6 hours ago [-]
I think they're just really old and not supported by anyone.
small_scombrus 5 hours ago [-]
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
Yokohiii 4 minutes ago [-]
What are the reasons why you want dark mode so badly?
TZubiri 5 hours ago [-]
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.
matthova 10 hours ago [-]
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
We have different definitions of lightweight it seems like.
frereubu 3 hours ago [-]
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!
chrismorgan 7 hours ago [-]
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.
steezeburger 8 hours ago [-]
Brb, gotta go cough up some mucss
ctippett 3 hours ago [-]
holiday.css for me, only 5kb to boot.
robertclaus 11 hours ago [-]
I like marx
needfish 6 hours ago [-]
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.
jrapdx3 10 hours ago [-]
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.
mikae1 4 hours ago [-]
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.
e12e 11 hours ago [-]
[2019]
But might be due a revival on the shoulders of LLMs.
9 hours ago [-]
boxed 4 hours ago [-]
It's sad that most of these themes makes buttons not look like buttons.
ctippett 4 hours ago [-]
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.
What does resetting inconsistent browser behavior have to do with classless styling? Those two aren't the same.
maxk42 10 hours ago [-]
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!
Rendered at 09:48:13 GMT+0000 (UTC) with Wasmer Edge.
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.
https://dohliam.github.io/dropin-minimal-css/
IMHO today dark mode support is part of reasonable defaults.
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
It's not that complex, there's some minimal frameworks here with 10kB of css code, it's ironic.
All the others are as you'd expect.
We have different definitions of lightweight it seems like.
Many had zero left/right margins on mobile.
Overall terrible defaults.
But might be due a revival on the shoulders of LLMs.