3 ms·
Why cannot people just assign the required width to the proper elements without polluting markup with those .grid_x classes is beyond me. One may just put some
by rimantas 16y ago
Why cannot people just assign the required width to the proper elements without polluting markup with those .grid_x classes is beyond me. One may just put some .top_left_red_link and .orange_button there as well then.
If you do it properly and want your .features element to take more space you just go to your CSS and adjust width: accordingly.
If you are using some "grid system", then you go to your markup and change .grid_2 to .grid_4. And when you change markup to change presentation instead of modifying CSS—you are doing something wrong.
- Semiapies 16y agoJust so, and when you can use all these grid classes and get their benefits transparently in the .less files without touching the markup, it's especially mystifying.
- kaylarose 16y agoThis. It is completely against the whole concept of separating markup from styling. I recently stumbled upon a pretty nice CSS "framework" (it's more of a starter template) that doesn't have all the crap most grid-frameworks have. It's ironically called Less Framework 3[1] (has nothing to do with LESS.js or the parent article). It basically boils down to a base adaptive-layout body width, and some comments that tell you the width you should make an element if you want it to span X columns on X screen/device width and adhere to a grid [1]http://lessframework.com/ http://lessframework.com/