Purecss.io – A set of small, responsive CSS modules by Yahoo
purecss.io
purecss.io
I'll make a superficial branch for some of my work and see how it ends up :)
Pros - I like the design of my site more (subjective) - Was much easier to grok, I found that working with the grid was very straightforward.
Cons - Ended up writing a lot more CSS than I would for a bootstrap site. - Not having a responsive sticky footer was a pain in the ass. I spent a lot of the day working through that.
Inuit is another framework that allows for this though it lacks in documentation and a user friendly website.
Oh please. Why not just a <button disabled>? So much redundancy and overly-verboseness for nothing.
"Namespacing" your CSS classes would make sense if you were actually composing element's style from multiple frameworks/libraries (vs. programming code), but that's not usually the case with CSS frameworks.
Have a .button class for styles of the button, font-family, height, width, border-radius, etc. You want _all_ .button elements to share this look and feel.
Then overwrite background colors, border colors etc on a button-primary, button-delete, etc classes.
It makes sense and it works.
Does PureCSS offer something missing in those 2 CSS frameworks?
1. It's lightweight.
2. It is stylistically plain.
3. The grid system is straightforward.
As mentioned, I just started with bootstrap and found grid to work just fine for my usecases. What problems/annoyances did you face when using other CSS frameworks (which you feel Pure avoids)?
Here for example there are no default paddings forced upon you.
It all depends on wether you know what you want, or just need "anything that works - doesn't matter how and what it does".
At some point I want to experiment with just how decoupled these big frameworks' grid systems are from the rest of the package. For example, can you use the following combinations:
Foundation 4 grid + Bootstrap 3 components
Bootstrap 3 grid + Topcoat components (Topcoat has no grid yet anyway)
Suzy grid + [Foundation 4 | Bootstrap 3 | Topcoat] components
etc.
I also want to performance test them all, using both Chrome dev tools [1] and Topcoat's Chromium Telemetry tests [2].
[1]: http://www.youtube.com/watch?v=Z1IqzeA3XXg
[2]: https://github.com/topcoat/topcoat/tree/master/dev/test/perf...
I don't know how Pure does nested because I haven't tried it, but from reading the docs, it looks like you just put a new .pure-g classed div inside whatever cell you are nesting inside, then put the nested units inside it.
http://purelang.bitbucket.org/
(Now I feel tempted to write an app that uses all three.)
An hour of looking at Pure, however, is enough to get started with confidence.
The grid classes are a bit strange to me though.
`pure-u-1-2` is "descriptive"? Not so much, unless you know the system.
any other advantages in using this??