1. It's lightweight.
2. It is stylistically plain.
3. The grid system is straightforward.
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)?
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...
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".
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.