Why do you use a framework rather than create your own grid?

Mark Boulton's Avatar

Mark Boulton

17 Feb, 2014 11:17 AM

I don't use a framework for grids for the same reason I don't use pre-defined colour palettes, or type combinations. For me, a grid is personal; to the content, to the brand, and to the device. I do, however, understand the reason for using frameworks where things 'just work'. Where you don't have to worry about Internet Explorer, or obscure HTML elements, or making forms work. Many frameworks do this really well, but where they don't work for me is where they start dictating the design output. And, unfortunately, I find most frameworks do that by declaring – most often – an even twelve column grid.

So, how about you? Why do you use a framework?

  1. 1 Posted by Ryan Rushing on 27 Apr, 2014 09:36 PM

    Ryan Rushing's Avatar

    Our team at Kalkomey uses Bootstrap for almost all products (a dozen content sites and several apps). The strength we find is the shallow learning curve and the ease in which work can be passed from one dev to another. I can build a site or app and get it out very quickly, and when another person works on it later, there is less need to decipher what's happening.

    One strength in frameworks may be the consistency, but arguably, that's also the weakness for the reasons you mentioned. Tomato/tomato, I guess.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac