Alternatives to Traditional CSS Grids

Dec 11, 2015 • Christopher McLean

We’ve all used them. The traditional twelve column grid, popularized through Bootstrap, have been used for years. In this article though, I want to explore some alternatives. Though the traditional 12 column grid is quite powerful, many developers use it as a crutch instead of searching for better solutions.

The Before Times

There was a time when we didn’t have CSS3, Sass, or LESS. We were just starting to move away from HTML tables for layout. The development of the grid system was a marvel of its time in the world of CSS. All of a sudden we could achieve the same layouts we were achieving with tables, but with far more control, and developed with web accessibility in mind.

This is what Bootstrap uses, and it’s a spitting image of what we all think of as the classic grid system.

They encouraged much tighter coupling of information structure and presentation logic.

The responsive breakpoints were baked in and had to be overwritten, often messily.

The classes are not semantically named.

Don’t get me wrong. These grids work and power some of the most powerful and influential web applications in the world. But, we can do better.

Enter Flexbox

Flexbox is fairly new, but it has one excellent selling point. Your grid system is native CSS. Yup! You can now setup grids with just native code and in about 20 lines of CSS. No Sass, LESS, or heavy framework, which means we can cut back on the number of dependencies in our styles.

By setting our display property to flex we get access to a ton of features built around setting up grids.

Here are just a few to give you an idea.

flex-wrap: Whether content wraps around a page

flex-direction: Whether content is in columns or rows

justify-content: How space around the container’s children is handled

With just two of these, we can make an element act like a grid with semantic classes.

Flexbox also allows us to be a lot more flexible with how our grids work and lets us make changes much more quickly. For example, if there was a client request to organize content by columns instead of in rows, this is all we would have to do.

Now, we did have to make some changes, but nothing too drastic. Also, our views only changed in the sense of needing to remove class attributes. The structure of our information didn’t change. As far as the CSS goes, we just deleted a few obsolete classes, added a container height, and told everything to act like columns.

With Bootstrap, this would involve a complete restructure of the HTML, as well as any CSS that may not agree with the new changes. Though still not a drastic change, it’s the far more disruptive scenario between the two.

The Catch

Flexbox still has really spotty support in Internet Explorer, with no support for IE8 and IE9, and partial support for IE10 and IE11. It can be great if your target is modern browsers, but not so much for legacy support.

Enter Sass Mixins

If flexbox isn’t your cup of tea or the right solution for you, many frameworks now include mixins that do most of the heavy lifting of a grid for you. A prime example would be Neat from Thoughtbot.

A Sass Mixin?

A Sass mixin is essentially a snippet of CSS you would see yourself using in multiple spots in your app. A common use case would be in wrapping up browser prefixes.

However, with libraries like Neat, we lose much of the flexibility that flexbox provides in making “table like” grids. For grid layouts with variable sized inner components, the struggle to minimize the effect of our CSS on our markup continues. This is because we are forced to introduce a new row element and class. Still, we do have the benefit of being able to name our own classes.

A Word On Flexible Public APIs

The main criticism against the traditional grid system is not in it’s power, but in how little control it actually give us. The hidden benefit in flexbox and mixin grid frameworks can be seen in the naming of our classes, allowing us to teat them as public APIs. We can choose to make class names semantic, include custom behavior beyond the scope of griding, and even treat our classes as adapters for third party libraries. The more we lean on native CSS and function/mixin libraries, the more resistant to change our codebase becomes and your fellow programmer will thank you for it.

Conclusion

In 2015, soon to be 2016, there are more options than just a single framework for building CSS grids. Though each solution has its ups and downs, they all aim to drastically improve the quality of our code. If you have the opportunity on a project, give one of these methods a try!