21–30 of 122 posts
Quite a lot of stylesheets in this simillar vein [0]. Basically doing CSS by using HTML5 semantic elements instead of classes. My personal favorite is Water.css [1], because it looks good and makes very good use of HTML5 semantics. Tacit [2] is also amazing. [0]: https://css-tricks.com/no-class-css-frameworks/ [1]: https://watercss.kognise.dev/ [2]: https://yegor256.github.io/tacit/
Earlier quoted context omitted.
> It is hard to take any stylesheet seriously when their website doesn't even properly use meta color scheme tags. I did my best looking at the source in my mobile browser, thinking they’d somehow misused the meta theme-color feature, but they haven’t used that at all. It seems your gripe is that they haven’t provided dark mode styles. Which is a reasonable gripe (and I provide them for my site even though I prefer l…
Yes, my gripe is that they are not using a prefers-color-scheme so that my browser properly uses dark mode and that some of the elements they use are not best practice. It is fair to say that I am not the most constructive person in doing so, but I also feel that by offering it as a framework they should already be aware of this.
I love mvp.css This made shipping my side project so much easier. I like that it’s opinionated and gets you going fast. You’re not really spending time picking colors, and you can focus on the content. This is the landing page I built: https://figmage.com
Quite a lot of stylesheets in this simillar vein [0]. Basically doing CSS by using HTML5 semantic elements instead of classes. My personal favorite is Water.css [1], because it looks good and makes very good use of HTML5 semantics. Tacit [2] is also amazing. [0]: https://css-tricks.com/no-class-css-frameworks/ [1]: https://watercss.kognise.dev/ [2]: https://yegor256.github.io/tacit/
I ask, because in the early days of css we also tried to use semantic style and had strange rendering issues on huge data tables and everytime, when the page had a lot of content. After trying a few things we came to the conclusion, that (especially but not only) IE had huge performance issues with semantic style. After switching to classes, everything worked fine. It technically made no sense, but since we did not change anything else, we came to the conclusion, that class based is faster than semantic...
Did anyone ever measure this for modern browsers?
Quite a lot of stylesheets in this simillar vein [0]. Basically doing CSS by using HTML5 semantic elements instead of classes. My personal favorite is Water.css [1], because it looks good and makes very good use of HTML5 semantics. Tacit [2] is also amazing. [0]: https://css-tricks.com/no-class-css-frameworks/ [1]: https://watercss.kognise.dev/ [2]: https://yegor256.github.io/tacit/
I remember loving a similar stylesheet for my personal blog, but ended choosing Tachyons because I wanted to have images alongside text(images aligned left, center right alongside text) that I couldn’t figure out how to do with such minimal css.. if anybody knows how, I’d be grateful!
Short question: Does anyone know about any performance issues using semantic vs class-based css? I ask, because in the early days of css we also tried to use semantic style and had strange rendering issues on huge data tables and everytime, when the page had a lot of content. After trying a few things we came to the conclusion, that (especially but not only) IE had huge performance issues with semantic style. After s…
Earlier quoted context omitted.
I remember loving a similar stylesheet for my personal blog, but ended choosing Tachyons because I wanted to have images alongside text(images aligned left, center right alongside text) that I couldn’t figure out how to do with such minimal css.. if anybody knows how, I’d be grateful!
align="right" wouldn't work?
Short question: Does anyone know about any performance issues using semantic vs class-based css? I ask, because in the early days of css we also tried to use semantic style and had strange rendering issues on huge data tables and everytime, when the page had a lot of content. After trying a few things we came to the conclusion, that (especially but not only) IE had huge performance issues with semantic style. After s…
Engines are now good enough you don’t really have to worry about selector performance unless you’re using ridiculously complex selectors, and even then the least efficient part is actually the layout calculation and painting.
This site is super simple and is super laggy on Safari Mac because they use awkward effects and animated gradient backgrounds, for example: https://colorjs.io/
Short question: Does anyone know about any performance issues using semantic vs class-based css? I ask, because in the early days of css we also tried to use semantic style and had strange rendering issues on huge data tables and everytime, when the page had a lot of content. After trying a few things we came to the conclusion, that (especially but not only) IE had huge performance issues with semantic style. After s…
https://frontstuff.io/you-need-to-stop-targeting-tags-in-css...