Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Future Friendly Style Guides

Luke Brooker
February 28, 2012

Future Friendly Style Guides

How style guides can help in a responsive design workflow.

Find out more here: http://blog.lukebrooker.com/future-friendly-style-guides

Pattern Response - Github
https://github.com/lukebrooker/pattern-response

Slides from my talk at What Do You Know - Brisbane: http://whatdoyouknow.webdirections.org/brisbane

Luke Brooker

February 28, 2012
Tweet

More Decks by Luke Brooker

Other Decks in Design

Transcript

  1. HOW I GET THERE • Wireframes - sketched only, multiple

    width. • Initial prototyping - very top level, mostly for a “live” feel of the layout from the wireframes, but able to be seen on many devices.
  2. HOW I GET THERE • Wireframes - sketched only, multiple

    width. • Initial prototyping - very top level, mostly for a “live” feel of the layout from the wireframes, but able to be seen on many devices. • Style tiles - design in Photoshop without “designing mockups” in Photoshop.
  3. “Websites are systems rather than pages and as soon as

    we stop perceiving them as that, the better.” ANNA DEBENHAM
  4. More than a STYLE GUIDE • Team Members - Document

    all components of a project and how to implement them.
  5. More than a STYLE GUIDE • Team Members - Document

    all components of a project and how to implement them. • Yourself - Keep as a starter style guide and another for a pattern library.
  6. More than a STYLE GUIDE • Team Members - Document

    all components of a project and how to implement them. • Yourself - Keep as a starter style guide and another for a pattern library. • Clients - Style guide, WYSIWYG Guide.
  7. • From wireframes - List out all components needed. •

    In the style guide - Add the structure (HTML) of each component.
  8. • From wireframes - List out all components needed. •

    In the style guide - Add the structure (HTML) of each component. • Design/style - Using the style guide or referencing your projects CSS as you build it.
  9. • From wireframes - List out all components needed. •

    In the style guide - Add the structure (HTML) of each component. • Design/style - Using the style guide or referencing your projects CSS as you build it. • Work together - Designers and developers can work together and discuss how things will work at different sizes.
  10. FOR EACH COMPONENT • Widths - how this component will

    react. How wide should it get before it’s layout changes.
  11. FOR EACH COMPONENT • Widths - how this component will

    react. How wide should it get before it’s layout changes. • Hierarchy - where this component will be used in the site, and how it react to others.
  12. FOR EACH COMPONENT • Widths - how this component will

    react. How wide should it get before it’s layout changes. • Hierarchy - where this component will be used in the site, and how it react to others. • Density - how the content changes as the component adapts to it’s surroundings. (will some things be hidden)
  13. FOR EACH COMPONENT • Widths - how this component will

    react. How wide should it get before it’s layout changes. • Hierarchy - where this component will be used in the site, and how it react to others. • Density - how the content changes as the component adapts to it’s surroundings. (will some things be hidden) • Interaction - will the way it is interacted with change as it changes.
  14. AND THAT IS WHAT I KNOW AN IDEA I HAD.

    ank you. @lukebroker