The new Ingrid 2.0 is here. This time around Ingrid's main focus is on prototyping / wireframing page layouts.
- Media queries for responsive layout support
- A SCSS version with a couple of neat customization settings
- Better structured class naming conventions, and…
- a bunch more column width variations.
Check out Ingrid in use at http://codepen.io/robertpiira/pen/kofpu. Or the plain demo page at http://codepen.io/robertpiira/full/kofpu
The previous Ingrid 1.0 will live on in its ingrid_1.0 branch.
So, The basic idea…
+-------------------[c]-------------------+
| +-------+ +-------+ +-------+ +-------+ |
| | | | | | | | | |
| | [u] | | [u] | | [u] | | [u] | |
| | | | | | | | | |
| +-------+ +-------+ +-------+ +-------+ |
+-----------------------------------------+
The container [c] needs two class-names:
.grid.grid--divide-4(or.grid--divide-3if there are 3 units).
Each unit [u] within the container [c] needs the class-name:
.grid_unit
To tweak the layout we can combine units like this.
+-------------------[c]-------------------+
| +-------+ +-------+ +-----------------+ |
| | | | | | | |
| | [u] | | [u] | | [u] | |
| | | | | | | |
| +-------+ +-------+ +-----------------+ |
+-----------------------------------------+
In this case the container [c] and units [u] have the same class-names as in the first example.
The difference is that we add the class name .grid_unit--span-2 on the last unit (making it span the width of two units).
The .grid_unit--span-x class-name can be used to combine units in any context (.grid--divide-2, .grid--divide-3, .grid--divide-4, etc.).
Units [f] that need to span the whole width of the container use the class .grid_field-unit
+-------------------[c]-------------------+
| +-------------------------------------+ |
| | [f] | |
| +-------------------------------------+ |
| +-------+ +-------+ +-------+ +-------+ |
| | | | | | | | | |
| | [u] | | [u] | | [u] | | [u] | |
| | | | | | | | | |
| +-------+ +-------+ +-------+ +-------+ |
+-----------------------------------------+
Ingrid includes classes that only respond to certain Media Query breakpoints. In this example container [c] is using the classes .m-grid and .m-grid--divide-2.
This is how the layout would look like on a narrow screen.
+-------------------[c]-------------------+
| +-------------------------------------+ |
| | [u] | |
| +-------------------------------------+ |
| +-------------------------------------+ |
| | [u] | |
| +-------------------------------------+ |
+-----------------------------------------+
…and once the breakpoint for .m-* prefixed class names kicks in for above narrow screens — the layout will reflow into two horizontally stacked columns.
+-------------------[c]-------------------+
| +-----------------+ +-----------------+ |
| | | | | |
| | [u] | | [u] | |
| | | | | |
| +-----------------+ +-----------------+ |
+-----------------------------------------+
.m-* prefixed classes are triggered for above small-sized viewports. "m-" is short for medium.
.l-* prefixed classes are triggered for above medium-sized viewports. "l-" is short for large.
Ingrid supports nested grids. Just remember when using em's or % units for gutters — these units are relative to the width or eventual font-size of the parent container.
The gutters are made by first giving the container [c] negative left and right margins.
Each unit [u] has a padding on each side that is equal to the containers [c] negative margins.
The gutters are set to a certain width in ingrid.css. But these measures can easily be overridden/tweaked to your own preference via your own classes that extend the container or directly in the ingrid CSS file.
The padding for the gutters work with em, % or pixel units (thanks to the CSS border-box box model).
Ingrid uses display: inline-block and border-box box model for laying out the individual units.
Border-box makes it easy to set borders and padding (for gutters) directly on units. (More on border-box http://paulirish.com/2012/box-sizing-border-box-ftw/.)
inline-block is just nice to work with and easy to reflow for different layouts.
The one negative with inline-block is the additional white-space that gets added between units. To remove the white-space evenly across different browsers can seem bit hacky. So Ingrid tries her best to get rid of the white-space. But the results are not cross-browser pixel-perfect. But really… Ingrid just doesn't care about pixel-perfection in that sense anymore. (More on display: inline-block at http://robertnyman.com/2010/02/24/css-display-inline-block-why-it-rocks-and-why-it-sucks/.)
If you'd like to try bits of Ingrid in production code, you could skip the whole .grid--divide-4 / .grid_unit--span-2 class names that Ingrid provides and make your own semantic class names for width hooks instead.
Ingrid 2.0 includes two breakpoints* and the CSS is structured in a mobile first approach. The first breakpoint is for "above mobile" (medium-sized screens/viewports) and the second is for "above tablet" (large-sized screen/viewports).
The breakpoints that are included with Ingrid can (and probably should) be modified so that they match your content.
*= To be correct, there are three breakpoints in total, for "The absence of support for @media queries is in fact the first @media query." —Bryan Rieger
Ingrid works with IE8 + and all modern browsers. IE6-7 are not supported.
All code licensed under CC0: http://creativecommons.org/publicdomain/zero/1.0/
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent