Very nice. I do have to wonder what the Web would have been like if browser default style sheets were less crappy and actually thought out like this.
Concrete.css
21–30 of 117 posts
Re: Concrete.css
#22Its fun and it looks good, but if you ever want to migrate away from it you pretty much have style everything all over? You can't just change the style of a a single tag?
Re: Concrete.css
#23Its fun and it looks good, but if you ever want to migrate away from it you pretty much have style everything all over? You can't just change the style of a a single tag?
Alternatively you can migrate to another classless framework and not change a thing :)
Re: Concrete.css
#24Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the disabled button greyed out.
I limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized v…
Opacity maybe would help here.
Re: Concrete.css
#25water.css[0] and pico.css[1] are some of my favorite classless css libraries. There's a full list of them here: https://github.com/dbohdan/classless-css [0]: https://watercss.kognise.dev/ [1]: https://picocss.com/
Water looks nice, I've not used that before.
I usually use https://classless.de because it supports theming, so I can add the bare minimum CSS to make it feel like a different site to another of my sites using it.
Re: Concrete.css
#26Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the disabled button greyed out.
I limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized v…
Could border-style dashed/dotted work?
Re: Concrete.css
#27Would this be more correctly called a CSS "stylesheet"?
Calling it a "CSS framework" really sent me in a loop trying to figure out what "framework" means.
Re: Concrete.css
#28Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the disabled button greyed out.
I limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized v…
Hatching seems an excellent idea.
Re: Concrete.css
#29Would this be more correctly called a CSS "stylesheet"? Calling it a "CSS framework" really sent me in a loop trying to figure out what "framework" means.
Modern CSS stylesheets include configurability via CSS variables on the root element so maybe that's where the "framework" comes from.
Also note: This project looks like an even more minimized version of PicoCSS [1]
Re: Concrete.css
#30Very nice. I do have to wonder what the Web would have been like if browser default style sheets were less crappy and actually thought out like this.
About the same as it is. My time working in web agencies has taught me that the vast majority of website owners don’t want to look the same as everyone else, and they want whizzbang high-tech widgets that make them look advanced. Usability all comes second to that.