| Some issues... Even using the grid normally, it ends up using more horizontal space than on the viewport, forcing a horizontal scrollbar (Chrome 18). Another problem: setting max-widths on units. Any proceeding units are handicapped by this and often just leave empty space to the right. I also don't like the presence of three sets of classes when two would be appropriate. "ingrid" as the container, and "span-x" for each column division. And this is unavoidable, as you need to define "in-[parts]" in the container to even use the span-x classes. I understand that it's less work if you stick to equal parts, but this is not the majority use case in my experience. I find the naming scheme awkward. "in-twos" and "in-thirds" instead of "in-halves" or "in-threes". Keep it consistent. --- All in all, I wouldn't recommend this to my mother. I use Nicole Sullivan's snippet in her github project,
https://github.com/stubbornella/oocss/blob/master/core/grid/... (demo: http://oocss.org/grids_docs.html) And it's been damn bullet proof, being used in production code. |