You’ve probably already heard about responsive design, which is website design that responds to the device constraints of the person viewing it. It’s a hot topic right now, and with good reason: alternative devices outsell desktop PCs 4 to 1 already, and within three years more Internet traffic in the US will go through mobile devices than through laptops or desktops.
All of this is forcing a convergence on what Jeremy Keith calls the “one Web”: a single Web that doesn’t care what device you’re on, how you’re viewing content or how you’re interacting with it.
What we found at ZURB was that while the concept of one Web is strong and the need for responsive websites great, the tools to help us quickly build that way just didn’t exist. That’s why we builtFoundation, a framework to help you build prototypes and production code that’s truly responsive.
The Problem with Global CSS
For years at ZURB, we used and refined a global CSS file that included a nice 960 grid, typography styles, buttons and other common elements. The trouble with our global CSS was that none of these pieces were written to be used by others, so they required a good deal of ramping up and training, with no great documentation.
Our CSS style guide had a lot of good global elements, but it wasn’t well documented, and it certainly wasn’t ready for other devices.
The bigger problem was that it wasn’t designed to be responsive or mobile-friendly in any way. We were stuck in the same rut that a lot of designers are in: creating a 1000-pixel-wide canvas, putting a 960 grid on it, and calling it a day. Our tools were built to support that workflow. So, we rewrote it into Foundation, a framework for everyone to be able to rapidly prototype in a responsive way.
Foundation is an MIT-licensed framework that includes a nestable arbitrary-width responsive grid; mobile styles, buttons and typography; layout affordances such as tabs and pagination; forms; and useful JavaScript plugins. We wrote or packaged all of these pieces to achieve a few goals:
- Quickly train new designers, inside and outside ZURB, to use a common framework;
- Rapidly prototype websites for desktops and any mobile device;
- Easily customize and complete the prototype to turn it into production code for particular projects or clients.
The first goal can’t be overstated; the value of having a single set of styles and best practices that the team can iterate on as a whole and communicate to our clients is tremendous. We can ramp up new designers much more quickly, build things faster and work together more easily. On one recent project, we even got a volunteer sufficiently up to speed on Foundation that we could collaborate on code?—?and it took only about 15 minutes.
So, How Does Foundation Work?
The core of Foundation can be summed up in a few points:
- A 12-column, percentage-based grid with an arbitrary maximum width.
The grid can be nested and used for quite complex layouts, and it works all the way back to IE 7. The grid reshuffles itself for smaller devices. - Image styles that disregard pixels.
Images in Foundation are scaled by the grid to different widths. - UI and layout elements.
Foundation includes common pieces such as typography and forms, as well as tabs, pagination, N-up grids and more. - Mobile visibility classes.
Rapidly prototyping is partly about having built-in functionality to tailor the experience. Foundation lets you very quickly hide and show elements on desktops, tablets and phones.
We deliberately built Foundation as a starting point, not as a style guide. We’ve included some styles to help you rapidly build something clickable and usable, but not something stylistically complete. Everything in Foundation is meant to be customized, including button styles, form styles (even custom radio, checkbox and select elements), typography, and layout elements such as tabs.
The Grid
A lot of grids are floating around, including some very good ones right here on Smashing Coding. Grid systems have a few issues, though, and we built Foundation to tackle them… well, some of them.
Fluidity
One of the critical pieces of device-agnostic design is having a fluid layout that conforms to the size (and orientation) of the device. Foundation’s grid is completely fluid, with percentage-based widths and margins, and it works all the way back to IE 7 (but not IE 6?—?philosophically speaking, acting like IE 6 doesn’t exist makes sense at this point). The HTML markup is pretty simple. Here’s an example of the grid in use, where we nest it for a more complex layout:
01 |
<div class="row"> |
02 |
<div class="eight columns"> |
03 |
<p>…</p> |
04 |
<div class="row"> |
05 |
<div class="six columns"> |
06 |
<h5>Another Section (.six.columns)</h5> |
07 |
<p>…</p> |
08 |
</div> |
09 |
<div class="six columns"> |
10 |
<h5>Another Section (.six.columns)</h5> |
11 |
<p>…</p> |
12 |
</div> |
13 |
</div> |
14 |
<p>Now the nested row has been closed, and we're back to the original eight-column section.</p> |
15 |
</div> |
16 |
</div> |
You can check out the above code on this example page.
Here are some of the built-in grid constructs, all of which scale with the browser window.
Responsiveness
The second critical piece is for the grid to be able to easily adapt to small devices and their unique constraints. We tackled this in three ways:
- On small devices (such as phones), the grid simply stacks vertically, with every column running the full width.
- We’ve also included block-grid classes, which are definitions for ULs that can be two-up through five-up and that remain a grid even on very small devices.
- And we have mobile visibility classes. These are a group of styles that enable you to quickly try things out by hiding and showing elements on different kinds of devices. You can attach classes like so:
1 |
<div class="hide-on-phones"> |
2 |
<p>This is a paragraph that we don't want to see on small devices.</p> |
3 |
</div> |
4 |
<div class="show-on-phones"> |
5 |
<p>This paragraph will be shown only on phones, not on tablets or desktops.</p> |
6 |
</div> |
Another interesting use for the classes is to prototype a common mobile consideration: placing mobile navigation at the bottom, as opposed to its more common placement at the top. You could do this:
01 |
<nav class="hide-on-phones"> |
02 |
<ul> |
03 |
<li><a href=#>…<a></li> |
04 |
<li><a href=#>…<a></li> |
05 |
<li><a href=#>…<a></li> |
06 |
</ul> |
07 |
</nav> |
08 |
… |
09 |
<nav class="show-on-phones"> |
10 |
<dl class="mobile tabs"> |
11 |
<dd><a href="#">…</a></dd> |
12 |
<dd><a href="#">…</a></dd> |
13 |
<dd><a href="#">…</a></dd> |
14 |
</dl> |
15 |
</nav> |
Foundation lets you write code once and show it on different devices easily.
Semantics
This one is tricky. A very compelling case is to be made that grid systems are by nature not semantic. This is partly true; they’re still descriptive of their function, but they do break the separation of data and display.
We didn’t want to base the Foundation framework on another extension, such as LESS. LESS is a great tool enabling you to use variables, shortcuts and more in your CSS, but we didn’t want to have to rely on it and add another barrier to using Foundation. The recent article we mentioned above actually fixed the data and display issue of grids by using LESS, which is awesome, but Foundation doesn’t fix that. Here’s why…
All of these methods are a stopgap. The replacement technique might come out next month or next year, but really all of these tools will change drastically in the very near future. Tools like LESS help us get a little closer to a very clean solution, but at a higher technology and learning cost. We wanted Foundation to be the fastest way to prototype for all kinds of devices, so we paid a small price for truly separated markup.
Rapid Prototyping Examples
Let’s look at a recent example for which Foundation was used. Every year, we do a 24-hour design marathon for a local non-profit, usually producing new marketing collateral and a new website. This year, we chose Rebekah Children’s Services, a great organization that helps with adoptions and takes care of disadvantaged kids.
This year, we wanted to build a website that was really responsive, and we had very little time to do it. Using just Foundation, we started prototyping the website based on some sketches we had done. In two hours, we managed to build this prototype.
Using Foundation, we built the prototype on the left in two hours (including every screen), and then started modifying it until it became the final website on the right.
It’s not terribly pretty, but it did give us something we could click around in, add copy to and iterate on. In the prototype, we used only a bare minimum of custom styles to more accurately represent the intended visuals.
Once we completed the prototype, we were able to complete the visual design and apply it to the existing Foundation code base to produce the final website. The final website retains all of Foundation’s framework, with the new styles applied on top of it.
How to Further Tailor the Experience
We recently launched an app through which to give traditional design feedback on mockups and websites. It’s called Spur, and it has been great fun for us; not only is it in our wheelhouse (for design feedback), but building a responsive Web app was an awesome opportunity.
Spur has a number of tools and actions, as well as some simple forms and a fairly complex JavaScript- and HTML-loading animation. Adapting all of this to mobile devices could have been really painful, but by starting with Foundation, we cut down on that considerably and prototyped the app quickly.
Spur on a desktop is different than Spur on a mobile device such as an iPhone.
Spur helped us get more comfortable with the constraints of a given device, including screen size, orientation, tap target size and copy. Spur is simpler on smaller devices, but it’s not stripped down. You can still capture a page, view it through the various filters, and share it with someone else.
Rapid Prototyping Is Required Now
The days of creating a blank Photoshop canvas and laying down a 960 grid are over, even if some of us are still working in that shared fantasy world. Mobile devices?—?or, let’s just say, devices beyond just laptops and desktops?—?are already prevalent and will only become more ubiquitous.
Don’t build a desktop website that’s pixel-perfect before thinking about other devices; get used to designing for several different sizes, and then quickly prototype your design to get a feel for the flow, function and interaction.
We built Foundation to help us do this faster and to develop better websites and apps for us and our clients. We feel so strongly about the need for this that Foundation is MIT-licensed and completely free to use, forever. If you try it out and have success with it, let us know. We’d love to hear about it, just as we’d love to hear about bugs or issues that you’ve run into.
We’re excited about this watershed moment in Web design (and in connectivity and data availability), and you should be, too: our industry will change more in the next three years than it has in its entire history. We hope this helps.
———–
Original Article By : ZURB , Source site : smashingmagazine.com
