77
AIGA ORLANDO DESIGNING FOR CMS Yesenia Perez-Cruz @YESENIAA Designer Allison Wagner @ALLIWAGNER Developer Thursday, January 17, 13

Designing for CMS 2013

Embed Size (px)

DESCRIPTION

Static, brochureware websites are a thing of the past. These days, as web designers, we work with dynamic content that will change countless times before, during, and after we hand off our work to clients. We're at a time where designing for Content Management Systems (CMS) is a must. In this lecture, Happy Cog's Allison Wagner and Yesenia Perez-Cruz will cover some best practices for designing CMS-driven websites, starting with square one, "What is a CMS?".

Citation preview

Page 1: Designing for CMS 2013

A I G A O R L A N D OD E S I G N I N G F O R C M S

Yesenia Perez-Cruz @ Y E S E N I A A

Designer

Allison Wagner @ A L L I WA G N E R Developer

Thursday, January 17, 13

Page 2: Designing for CMS 2013

CLIENTS

Thursday, January 17, 13

Page 3: Designing for CMS 2013

AN EVENT APARTThursday, January 17, 13

Page 4: Designing for CMS 2013

A LIST APARTThursday, January 17, 13

Page 5: Designing for CMS 2013

Thursday, January 17, 13

Page 6: Designing for CMS 2013

Thursday, January 17, 13

Page 7: Designing for CMS 2013

“I want to be able to update the site myself”

- e v e r y c l i e n t , e v e r

Thursday, January 17, 13

Page 8: Designing for CMS 2013

CMS FTW OMG1

A I G A O R L A N D O

Thursday, January 17, 13

Page 9: Designing for CMS 2013

An interface toadd/update

content on the web

Thursday, January 17, 13

Page 10: Designing for CMS 2013

VIA TRENT WALTON,HTTP://TRENTWALTON.COM/

Thursday, January 17, 13

Page 11: Designing for CMS 2013

BACK-END FRONT-ENDThursday, January 17, 13

Page 12: Designing for CMS 2013

P.O.D.E.Publish Once Distribute Everywhere

Thursday, January 17, 13

Page 13: Designing for CMS 2013

Thursday, January 17, 13

Page 14: Designing for CMS 2013

Home

Thursday, January 17, 13

Page 15: Designing for CMS 2013

News

Thursday, January 17, 13

Page 16: Designing for CMS 2013

List

Thursday, January 17, 13

Page 17: Designing for CMS 2013

RSS Feed

Thursday, January 17, 13

Page 18: Designing for CMS 2013

AVOIDINGBOTTLENECKS

Thursday, January 17, 13

Page 19: Designing for CMS 2013

KNOW YOURROLE

• Content Providers

• Content Publishers

• Super Editors

Thursday, January 17, 13

Page 20: Designing for CMS 2013

VERSIONCONTROL

Thursday, January 17, 13

Page 21: Designing for CMS 2013

INTO THE SUNSET

Thursday, January 17, 13

Page 22: Designing for CMS 2013

Design Systems2

A I G A O R L A N D O

Thursday, January 17, 13

Page 23: Designing for CMS 2013

YOU CAN’T DESIGN EVERY PAGE

Thursday, January 17, 13

Page 24: Designing for CMS 2013

SITE MAP

Thursday, January 17, 13

Page 25: Designing for CMS 2013

SITE MAP

Thursday, January 17, 13

Page 26: Designing for CMS 2013

THINK MODULARLY

Thursday, January 17, 13

Page 27: Designing for CMS 2013

LAYOUTS: THE FOUNDATIONThursday, January 17, 13

Page 28: Designing for CMS 2013

MODULES: THE BUILDING BLOCKSThursday, January 17, 13

Page 29: Designing for CMS 2013

Thursday, January 17, 13

Page 30: Designing for CMS 2013

Thursday, January 17, 13

Page 31: Designing for CMS 2013

Thursday, January 17, 13

Page 32: Designing for CMS 2013

Thursday, January 17, 13

Page 33: Designing for CMS 2013

MOMMY, WHERE DO MODULES COME FROM?

Thursday, January 17, 13

Page 34: Designing for CMS 2013

PROJECT DEFINITIONWhere User Needs and Business Requirements Intersect

Thursday, January 17, 13

Page 35: Designing for CMS 2013

R E Q U I R E M E N T S G AT H E R I N G :

Define user needs & business goals

Thursday, January 17, 13

Page 36: Designing for CMS 2013

REQUIREMENTS DOCUMENT

Thursday, January 17, 13

Page 37: Designing for CMS 2013

B U S I N E S S G O A L :

Display upcoming events to encourage users to visit the website frequently and stay informed.

M O D U L E :

Events Module

Requirements Inform Modules

Thursday, January 17, 13

Page 38: Designing for CMS 2013

HTMLPrototype

• Show Interactions

• Responsive

• Low !delity

• Hierarchy

Thursday, January 17, 13

Page 39: Designing for CMS 2013

TWITTER.GITHUB.COM/BOOTSTRAP/

Thursday, January 17, 13

Page 40: Designing for CMS 2013

RESPONSIVE

Thursday, January 17, 13

Page 41: Designing for CMS 2013

L I S T O F M O D U L E S :

NavigationSocial Media

Account InformationNews Events

Did You Know? contentSearch Results

Stock TickerPresentations

WorkshopsCurrent Outages

etc, etcThursday, January 17, 13

Page 42: Designing for CMS 2013

M O D U L E S PA G E T Y P E S

Thursday, January 17, 13

Page 43: Designing for CMS 2013

M O D U L E S PA G E T Y P E S

Thursday, January 17, 13

Page 44: Designing for CMS 2013

M O D U L E S PA G E T Y P E S

M O B I L E

TA B L E T

Thursday, January 17, 13

Page 45: Designing for CMS 2013

SITE MAP

Thursday, January 17, 13

Page 46: Designing for CMS 2013

Design Process3

A I G A O R L A N D O

Thursday, January 17, 13

Page 47: Designing for CMS 2013

Thursday, January 17, 13

Page 48: Designing for CMS 2013

Style Tiles

• Quick

• Layout agnostic

Thursday, January 17, 13

Page 49: Designing for CMS 2013

STYLETIL.ES

Thursday, January 17, 13

Page 50: Designing for CMS 2013

Type System

• Tailored to your content

• Mobile !rst

• typecast.com

Thursday, January 17, 13

Page 51: Designing for CMS 2013

TYPECAST.COM

Thursday, January 17, 13

Page 52: Designing for CMS 2013

Grid• Foundation

• Future-thinking

• Flexible

• Eliminates indecision

Thursday, January 17, 13

Page 53: Designing for CMS 2013

MODULARGRID.ORG

Thursday, January 17, 13

Page 54: Designing for CMS 2013

Grayboxes

• Basic sketches of your layouts

• Ensure that your system will have range

Page Title

NEWS & EVENTS

CENTERS & INSTITUTES

JOURNALS

RELATED LINKS

Page Title

CENTERS & INSTITUTESJOURNALSRELATED LINKS

Page Title

A B C

Page Title

NEWS & EVENTS

CENTERS & INSTITUTES

JOURNALS

RELATED LINKS

Page Title

CENTERS & INSTITUTESJOURNALSRELATED LINKS

Page Title

D E F

Thursday, January 17, 13

Page 55: Designing for CMS 2013

Design Blitz

• Designing all the things!

Thursday, January 17, 13

Page 56: Designing for CMS 2013

Home Page

Thursday, January 17, 13

Page 57: Designing for CMS 2013

Primary Subpage

Thursday, January 17, 13

Page 58: Designing for CMS 2013

Long-formContent

Thursday, January 17, 13

Page 59: Designing for CMS 2013

SearchResults

Thursday, January 17, 13

Page 60: Designing for CMS 2013

Extensibility 4

A I G A O R L A N D O

Thursday, January 17, 13

Page 61: Designing for CMS 2013

ORDER & REPETITIONMake deviations purposeful

Thursday, January 17, 13

Page 62: Designing for CMS 2013

DESIGN SYSTEM AT WORK

Thursday, January 17, 13

Page 63: Designing for CMS 2013

XThursday, January 17, 13

Page 64: Designing for CMS 2013

DESIGN SYSTEM AT WORK

Thursday, January 17, 13

Page 65: Designing for CMS 2013

Thursday, January 17, 13

Page 66: Designing for CMS 2013

Thursday, January 17, 13

Page 67: Designing for CMS 2013

PLAN FOR THINGS BREAKING DOWNThey will.

Thursday, January 17, 13

Page 68: Designing for CMS 2013

General Styles

• Helps !ll in the gaps that may not have been designed

Thursday, January 17, 13

Page 69: Designing for CMS 2013

PLAN FOR VARIATION

Thursday, January 17, 13

Page 70: Designing for CMS 2013

PLAN FOR VARIATION

Thursday, January 17, 13

Page 71: Designing for CMS 2013

PLAN FOR VARIATION

Thursday, January 17, 13

Page 72: Designing for CMS 2013

Putting the System to work5

A I G A O R L A N D O

Thursday, January 17, 13

Page 73: Designing for CMS 2013

Template BuildCMS Setup

Client Gathers Content

Thursday, January 17, 13

Page 74: Designing for CMS 2013

PORTINGCONTENT

Thursday, January 17, 13

Page 75: Designing for CMS 2013

BadContent Entry

Thursday, January 17, 13

Page 76: Designing for CMS 2013

GoodContent Entry

Thursday, January 17, 13

Page 77: Designing for CMS 2013

THANK YOU! Yesenia Perez-Cruz @ Y E S E N I A A

Designer

Allison Wagner @ A L L I WA G N E R Developer

Thursday, January 17, 13