Would like to know your thoughts.
I've been tweaking a grid system that I have been working on and experimenting with for a year or so and it changes every time I use it and gets a little better.
It started as an inline-block grid but I ran into some maintainability issues with largish CMS projects and I switched it to a grid based on floats. It uses border box sizing and percentages and it seems to be working fairly well on some recent projects.
Recently I've been experimenting with a grid API written in Sass, which generates your responsive grid based on the breakpoints you set and that has been pretty successful for being able to set up, extend and tweak the grid to get it just right.
I'd like the hear some of your issues with using inline-block. I've been using them a lot without much issues.
We use Bourbon + Bitters for our grid framework. It removes the need for
span-nclasses like Bootstrap, which we think is better since it cleans up the HTML considerably.
...and the fact that bourbon, bourbon neat, and bourbon bitters are split out is nice. I don't need all three on EVERY project.
Previously: Blueprint CSS.
Now: Nothin’. Box-sizing: border-box; means it’s easy to mix percentages and pixels, which makes responsive grids pretty simple just using percentages.
Been using the stylus port of Jeet lately and it's great, https://github.com/mojotech/jeet
Allows for really flexible grids in your css similar to bourbon's neat or bitters.
Bootstrap's grid system - for whether I'm just designing or designing + developing.
I know it, and it's interoperable with pretty much anyone who does front-end development.