Clients sign off on designs. You build a website for them based on these designs. It looks quite like the designs, but not exactly like this. It's not your fault. It's not the client's fault. But wouldn't it be nice if you could build what the client signed off on?
In this session I'll look at lambasting my most hated design tool - Photoshop. In short, it's for editing photographs, not designing websites.
Then I'll talk a little about something more modern - SketchApp - built especially for designing user interfaces, but still falls waaaay short when you want to give your clients designs that they can touch and feel and smell and see exactly what they are going to get.
Following, I'll talk about "Design for the Browser" and/or "Design in the Browser". Basically, using modern tools such as PatternLab and Component-based design principles to give your clients an interactive prototype of exactly what their final product will look like. Not an approximation of it, the thing itself - so the product they get is the product they sign off on.
Clients can test this design on phones, tablets, watches - heck, even computers! - and make sure it works before they get you to implement it.
Finally, we'll see how these static prototypes can be integrated with Drupal, so that the template of the mockup is the template used by Drupal - again, to make sure the design that is signed off on is the design that is delivered. No compromises. No surprises.