Lightweight => 10 KB I'm actually more looking for a grid system using flex in a few bytes
It's written is Sass, you can simply import only the components that you need such as the grid.
Spectre.css – A Lightweight, Responsive and Modern CSS Framework
41–50 of 135 posts
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#42The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…
From what I understand CSS frameworks used to make web dev more bareable because you could just use a simple class name and the framework would apply a load of hacks to get something sensible that works in all browsers. Bootstrap always seemed like a polyfil for flexbox.
Bootstrap 4 now actually uses flexbox
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#43I prefer https://tachyons.io/ as a CSS framework that avoids any pre-styled themes and just provides building blocks. Great for SPA/component UIs.
Anyone interested in this approach may also like Tailwind https://tailwindcss.com/
How is this different from inline styling ? this throws class inheritance out of the window
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#44Looks good, I'll use it!
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#45Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#46Are there by chance any samples with Arabic in this framework? Hoping it resolves the large size disparity between Latin and Arabic font sizes
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#47I prefer https://tachyons.io/ as a CSS framework that avoids any pre-styled themes and just provides building blocks. Great for SPA/component UIs.
I don't like that concept of essentially inlining styles in the class attribute. It is just a misuse of html classes.
Class names should be used sparingly and describe the semantics of an element rather than its visual appearance. It should be something like class="button submit disabled" instead of class="f6 link dim br1 ph3 pv2 mb2 dib white bg-black".
If anything these styles should be exposed as sass mix-ins that you can use in your own styles. So you have a named set of style mix-ins that do not pollute class names.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#48The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…
As a "non-fluent CSS user", I find it challenging and frustrating to maintain visual consistency and cross-browser compatibility without frameworks. I totally appreciate the fact it's me being lazy to really learn CSS who is at fault.
Think of it like different construction methods - you can build something, let's say the Pyramids, or you can take something already built and beautiful, but is not what you need, and slowly curve Petra inside the walls. Both work.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#49Earlier quoted context omitted.
Tailwind is absolutely fantastic. I can code CSS 2-3 times faster and I no longer hate doing it.
How do we classify the progression that is tachyons/tailwind? Each time I see a new CSS framework I also think, is this yet another framework for devs that can’t desigh or is someone working to move the needle beyond what tachyons/tailwind have set a new place of maintainable CSS.
> How do we classify the progression that is tachyons/tailwind? Each time I see a new CSS framework I also think, is this yet another framework for devs that can’t desigh or is someone working to move the needle beyond what tachyons/tailwind have set a new place of maintainable CSS.
AFAIK, functional CSS frameworks like Tailwind are getting relevance thanks to the recent boom of functional programming.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#50The more web development I’ve done the more I’ve swung back to just writing CSS myself rather than depending on CSS frameworks; I’ve ended up seeing these less as ways to accelerate development for a team that is skilled at frontend, but instead as a way for people who don’t like styling or have little experience in frontend development/low design sense to style things reasonably. But I keep seeing frontend framework…
What, not even SASS/SCSS?