Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

CSS

Can we build it better?

So most all of us have used Bootstrap or Foundation and they work fairly well each has their strengths and weaknesses. I stumbled upon this article yesterday (maybe the day before) about using grid systems and then using the CSS calc() to determine the width of a column in a grid.

http://webdesign.tutsplus.com/tutorials/calc-grids-are-the-best-grids--cms-22902

I've often wanted to tackle building a front-end framework but it really is a massive task for one guy to do. Especially if like me, you're no guru on the subject. So why not reach out and at the very least talk about it.

One of my biggest 'peevs' with the current convention is that with Bootstrap for example you want a single column that spans the width of its container, you want one (1) column so you call a class of 'col-sm-12' or even with Guil Hernandez's poly-ui kit (awesome sauce btw) you call 'grid__col--12'.

I've always wondered why you wouldn't call one (1) column if you want one column 'col-sm-1' or 'grid_col--1' and if you want 12 columns call 'col-sm-12' or 'grid_col--12'.

There is a slight issue with math it works fine if you were developing a style sheet for a one off project and you know you need one column that is 12/32nds and another in the same row that's 22/64ths of the containing element but in something that is meant to be used by the masses it get hairy with unequal columns in a given row.

https://github.com/johnweland/grids

Why take on a full frontend framework though? Well as I said the aforementioned frameworks are great they work, but to utilize something like a 'navbar' which lays out perfect but them change the styling of it to match your theme needs you have to overwrite a tone of code (bad idea) or rewrite a ton of code in a new stylesheet to override. There has to be a better way.

1 Answer

Frameworks will continue to evolve, but here are a few of my favorites.

Those are all great and I know nothing is going to be future proof for many reasons. The biggest reasons I feel are that while the web languages get standardized (e.g HTML5 or CSS3) they don't ever fully get implemented in to the browsers and even the things that do get implemented each of the browsers has its own interpretation. So in that sense we can future proof in a given language version let alone withing a given language as a whole. BUT I still think we can do better.