Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

General Discussion

Jason Narog
Jason Narog
14,611 Points

Sass grid and vertical rhythm system feedback

Hi all,

To better understand some of the concepts regarding grid systems and Sass, I put together a series of mixins and functions to set up fluid, adaptive, and static grids with varying levels of media query support. I later added on additional support for vertical (and as an after thought horizontal) rhythm to try and keep everything flowing. The grid supports ems or % depending on what someone is using and the vertical rhythm supports rems, px, and ems.

I wanted to share this with everyone and see if it could be built upon to fix any sort of bugs or improve upon the UI as its being developed in isolation at the moment.

https://github.com/pokermoneyclips/lazygrid

I'm currently aware of 2 bugs: Nesting input is backwards (ie 2 returns 4 and 4 returns 2 for grid count) Vertical rhythm for bottom border is not returning correctly when both top and bottom margins are present

Thanks

2 Answers

James Barnett
James Barnett
39,199 Points

Have a look at neat & Susy for some good ideas.

Jason Narog
Jason Narog
14,611 Points

I actually already have almost everything neat has built in except for the coloring of the grids and the zeroing out of margins / padding, although I do zero out a margin on the first and last of the nested grids. Susy looks like they already upgraded to use the mapping feature of Sass 3.3 so they're way ahead of me there. Sounds like way better documentation on the readme file is whats needed most on my part to better describe what my system does.