Thursday, August 25, 2011 - Drupal...THE KICK-OFF Supply the designer with a list of common items...

Post on 08-Aug-2020

1 views 0 download

Transcript of Thursday, August 25, 2011 - Drupal...THE KICK-OFF Supply the designer with a list of common items...

Thursday, August 25, 2011

Thursday, August 25, 2011

A bulletproof approach to theming

Presented by Rasmus Kalms

Design, UX and Theming

Thursday, August 25, 2011

Thursday, August 25, 2011

STATE OF THEMING

How do you define yourself as a themer?

Thursday, August 25, 2011

Goals for this talk

Thursday, August 25, 2011

NO SILVER BULLETS

preprocess_make_it_all_go_away();

Thursday, August 25, 2011

CASE #01

Bad timing and the indifferent backend dev, with little to no interest in presentation or markup

Thursday, August 25, 2011

So, how do we deal with these scenarios?

Thursday, August 25, 2011

LET YOUR THEMER ASK

Does the output match the intended design?

Thursday, August 25, 2011

SHARING IS CARING

How do we improve communication?

Thursday, August 25, 2011

REMEMBER

Thursday, August 25, 2011

• Focus on how you can make a difference from your point-of-view.

REMEMBER

Thursday, August 25, 2011

• Focus on how you can make a difference from your point-of-view.

• Ensure consistent communication and regular meetings, with output and code reviews.

REMEMBER

Thursday, August 25, 2011

Style guides and Drupal

Thursday, August 25, 2011

A style guide or style manual is a set of standards for the writing and design of

documents... The implementation of a style guide provides uniformity in style and

formatting of a document.

FROM WIKIPEDIA.ORG:

http://en.wikipedia.org/wiki/Style_guide

Thursday, August 25, 2011

BASICALLY

A style guide is a document describing a set of visual standards.

Thursday, August 25, 2011

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

• Description of logo usage

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

• Description of logo usage

• Colorschemes

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

• Description of logo usage

• Colorschemes

• Typography

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

• Description of logo usage

• Colorschemes

• Typography

• Grids

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

• Description of logo usage

• Colorschemes

• Typography

• Grids

And so on...

A STYLE GUIDE COULD BE

Thursday, August 25, 2011

Skype brand style guideLocate it here: http://bit.ly/9oksav

Thursday, August 25, 2011

BENEFIT

It ensures consistent usage of deliverables

Thursday, August 25, 2011

PRINT VS. DEVELOPMENT

How could we use style guides in a Drupal environment?

Thursday, August 25, 2011

The typical workflow

Thursday, August 25, 2011

THE KICK-OFF

Supply the designer with a list of common items like typography, lists, form elements etc.

Thursday, August 25, 2011

THE KICK-OFF

Pinpoint common design elements like content boxes (panels) and lists (views) together

Thursday, August 25, 2011

SPECIFICALLY

Thursday, August 25, 2011

• Typography

SPECIFICALLY

Thursday, August 25, 2011

• Typography

• Grid / baseline

SPECIFICALLY

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

SPECIFICALLY

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

SPECIFICALLY

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

• Use of color

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

• Use of color

• Navigation & links

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

• Use of color

• Navigation & links

• Images (usage)

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

• Use of color

• Navigation & links

• Images (usage)

• Taxonomy and teaser lists

Thursday, August 25, 2011

• Typography

• Grid / baseline

• Lists (views)

• Form elements

• Buttons

SPECIFICALLY

• Use of color

• Navigation & links

• Images (usage)

• Taxonomy and teaser lists

DEFINE MARGINS, DIFFERENT STATES (I .E LINKS & FORMS), POSITIONING ETC.

Thursday, August 25, 2011

Thursday, August 25, 2011

Thursday, August 25, 2011

VALUABLE NOTES ABOUT IA

How we use Information Architecture at Peytz & Co.

Thursday, August 25, 2011

HEADER

SIDEBAR

FOOTER

CONTENT

NAV

NODE

NODE SEC. NAV

SEARCH

NODE BLOCK

NODE

Thursday, August 25, 2011

KEEPING CONTENT CONSISTENT

If the project warrants it, you should keep a list of intended output for each page

Thursday, August 25, 2011

PAGE DESIGN VS. CONTENT SYSTEMS

The benefit is the replacement of page design in Photoshop, with the design of content systems in Drupal

Thursday, August 25, 2011

The standard theme or boilerplate

Thursday, August 25, 2011

REMEMBER

Thursday, August 25, 2011

• Create a style guide, and keep using and maintaining it.

REMEMBER

Thursday, August 25, 2011

• Create a style guide, and keep using and maintaining it.

• Make sure the site has a strong, well-defined information architecture. Help maintain it!

REMEMBER

Thursday, August 25, 2011

• Create a style guide, and keep using and maintaining it.

• Make sure the site has a strong, well-defined information architecture. Help maintain it!

• If you’re providing a client with a theme for Drupal, you should make sure it works on even the most basic Drupal installation.

REMEMBER

Thursday, August 25, 2011

Code Structure

Thursday, August 25, 2011

CODE STRUCTURE

Divide templates into folders like “views”, “panels”, “nodes” etc.

Thursday, August 25, 2011

CODE STRUCTURE

Use Drupal’s module architecture and avoid bloat

Thursday, August 25, 2011

My small crisis of faith as a front-end developer

Story time!

Thursday, August 25, 2011

Using HTML5/CSS3 doesn’t have to be complicated

Thursday, August 25, 2011

CLEAR BENEFITS

It’s fast and it keeps the code flexible; less need for cutting out graphics in Photoshop

Thursday, August 25, 2011

CLEAR BENEFITS

Leaves more room for prototyping and an iterative approach

Thursday, August 25, 2011

Adaption and ease of use

Thursday, August 25, 2011

LE SIGH (VENDOR PREFIXES)

-moz-border-radius: 4px;

-webkit-border-radius: 4px;

-o-border-radius: 4px;

... and on and on.

Thursday, August 25, 2011

LESS VS. SASS

CSS pre-processors

Thursday, August 25, 2011

THEY TYPICALLY PROVIDE

Thursday, August 25, 2011

• Variables

THEY TYPICALLY PROVIDE

Thursday, August 25, 2011

• Variables

• Mixins

THEY TYPICALLY PROVIDE

Thursday, August 25, 2011

• Variables

• Mixins

• Functions

THEY TYPICALLY PROVIDE

Thursday, August 25, 2011

• Variables

• Mixins

• Functions

• Nesting

THEY TYPICALLY PROVIDE

Thursday, August 25, 2011

VARIABLES EXAMPLE

@color: #4D926F;

#header { color: @color;}

h2 { color: @color;}

Thursday, August 25, 2011

MIXINS: LIKE VARIABLES WITH CLASSES

.rounded-corners (@radius: 5px) { border-radius: @radius; -webkit-border-radius: @radius; -moz-border-radius: @radius;}

#header { .rounded-corners;}

#footer { .rounded-corners(10px);}

Thursday, August 25, 2011

NESTED RULES: SIMPLE INHERITANCE

#header { h1 { font-size: 26px; font-weight: bold; } p { font-size: 12px; a { text-decoration: none; &:hover { border-width: 1px } } }}

Thursday, August 25, 2011

FUNCTIONS

@the-border: 1px;@base-color: #111;@red: #842210;

#header { color: @base-color * 3; border-left: @the-border; border-right: @the-border * 2;}

#footer { color: @base-color + #003300; border-color: desaturate(@red, 10%);}

Thursday, August 25, 2011

Is there a module for this? Yes!

Thursday, August 25, 2011

Is there a module for this? Yes!

• http://drupal.org/project/sass

Thursday, August 25, 2011

Is there a module for this? Yes!

• http://drupal.org/project/sass

• http://drupal.org/project/less

Thursday, August 25, 2011

FINAL NOTE

Organizing your theme and approach goes a long way

Thursday, August 25, 2011

THEMERS

Take it upon yourself to communicate the constraints and possibilities

Thursday, August 25, 2011

Your designers should be running their own projects. Do not place some non-designer in

between them and their client. You have a responsibility to shepherd your designers

toward consummate professionalism. (...) To do otherwise is to cripple their professional development; perhaps permanently.

TO QOUTE ANDY RUTLEDGE:

From “Design Professionalism”, designprofessionalism.com

Thursday, August 25, 2011

Thank youIf you want to catch up: @kalms on Twitter

Thursday, August 25, 2011

Thursday, August 25, 2011

What did you think?

Thursday, August 25, 2011

What did you think?Locate this session on the DrupalCon London website:http://london2011.drupal.org/conference/schedule

Thursday, August 25, 2011

What did you think?Locate this session on the DrupalCon London website:http://london2011.drupal.org/conference/schedule

Click the “Take the survey” link

Thursday, August 25, 2011

THANK YOU!

What did you think?Locate this session on the DrupalCon London website:http://london2011.drupal.org/conference/schedule

Click the “Take the survey” link

Thursday, August 25, 2011