We’ve all seen margin: 0 auto; for horizontal centering, but margin: auto; has refused to work for vertical centering… until now! But actually (spoiler alert!) absolute centering only requires a declared height* and these styles:
There has been a fantastic response to the post on the Dribbblisation of Design, many people agreeing with the premise and adding to it, some disagreeing and offering counter points. I want to respond to people’s commentary, explain the original motivation for the post which wasn’t about Dribbble specifically, and talk about how we hire designers.
Designing and developing can be time-consuming without a workflow, especially when the project involves a new challenge, putting the team or freelancer into unknown territory. Moreover, time is a key factor in productivity. Working efficiently enables us to deliver better value at a competitive price.
When you buy something, I bet you want it to work. Heck, even if you use something for free — maybe borrowed from a friend — I bet you want it to work. No one prefers hiking boots that are too tight (or too loose), a car that shimmies when you drive faster than 40 miles an hour, or a kitchen knife that can’t cut a tomato. And Web designers don’t prefer a web font that doesn’t fit a project, fall apart in different browsers or can’t be used in a mock-up.
I’ve been thinking about workflows for Responsive Web Design quite a bit, particularly since its now become our default approach on every new project – similar to Cloud Fours recent change of heart. I’ve been especially influenced by two recent articles on the topic, namely Dennis Kardys’s A More Flexible Workflow, and Viljami Salminen’s Responsive workflow.
I struggled a bit to make their approaches fit into how we worked, so I decided to expand on what they’ve done and draw something that reflects a bit more accurately how we are incorporating Responsive Web Design into a user-centered workflow within an agency model. It’s not perfect by any means, but here’s what I came up with.