Spectre.css – A Lightweight, Responsive and Modern CSS Framework

Post by [deleted] » Thu, Nov 08, 2018, 3:05 PM UTC

pbhjpbhj wrote: post #85

trixn wrote: post #67

Earlier quoted context omitted.

I agree that you could in a lot of cases get along without these classes. But sometimes you want e.g. an anchor acting as a button in a web application. Or you want a button element with browser styles. You could argue that this is also already an anti-pattern but it does way less harm then leaking inline styles into the namespace and it is still semantic. Also this was just an example (maybe not the best one) to ill…

is selectable with [disabled] { } or [disabled="disabled"] { } And [disabled]:not(.greyButtonStyle) { } does the last example if you classed that style, doesn't it? I've only done a little CSS, not very recent ... unless you're recruiting, then I'm an expert ;o). I imagine though there are times when you want to class (some) button tags as .button.

Post by matt_lo » Thu, Nov 08, 2018, 3:32 PM UTC

Post by grouchoboy » Thu, Nov 08, 2018, 3:40 PM UTC

Chetan496 wrote: post #76

Touche wrote: post #66

Earlier quoted context omitted.

I think you're probably still thinking about CSS as it was 5 years ago. When you had to do weird hacks to get things the way you wanted them. Modern CSS is much easier. In fact, if you are sticking .row and .column everywhere you are doing considerably more work than just to define a grid layout using display: grid once in your CSS, and then just use semantic HTML thereafter.

While the grid and flexbox have made things better, the display:grid is still not supported in IE 11 very well. The grid css model was implemented in IE very early but as the specification got updated, IE remained with a different(older and incompatible) implementation of display:grid. Of course, we can still make display:grid work in IE11 by some additional work. But this is an additional overhead. Flexbox has very…

Post by Zelphyr » Thu, Nov 08, 2018, 3:49 PM UTC

cptskippy wrote: post #78

osdiab wrote: post #23

The 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…

While I share your sentiment about frameworks, I work in enterprise app development and I can't remember the last time I encountered someone else who had a firm grasp of CSS or even the Frameworks. Our organization adopted Bootstrap because it's a consistent and familiar framework and it takes less time for the inexperienced developers (most in my experience) to come up to speed on an app. When you have 20 developers…

Post by calibas » Thu, Nov 08, 2018, 3:52 PM UTC

koboll wrote: post #72

codyeatworld wrote: post #9

What I enjoy about Spectre.css is that there is no javascript and the CSS is readable. It's easy to drop their CSS into a react component and extend it because it's so readable.

If you hover the homepage buttons, you can see they veeery slightly change color, to a different shade of purple. It's barely perceptible. Breaking fundamental rules of user experience right off the bat is not a good sign when I'm evaluating a CSS dependency.