Responsive Web Design Process

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

www.responsiveprocess.com

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

www.helloﬁsher.com

Slide 8

Slide 8 text

I believe that what I do saves the world (one web project at a time)

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

Going to talk about the process.

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

Image source: palantir.net

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

http://youtu.be/ha-uagjJQ9k I must have neurolized myself to keep the information from myself.

Slide 21

Slide 21 text

Web standards is not the old busted hotness. It is part of the new hotness of RWD.

Slide 22

Slide 22 text

Discovery

Slide 23

Slide 23 text

http://youtu.be/eunaclr-WgU (getting to know the baseline story)

Slide 24

Slide 24 text

First things first: let’s meet up and get to know each other. From our early meetings and research, we'll establish communication protocols, milestones and timelines, deliverables and scope, roles and expectations.

Slide 25

Slide 25 text

Slide 26

Slide 26 text

You want to know who you are working with... Project planner

Slide 27

Slide 27 text

Project analysis. We will work with you to help determine the requirements of the project, from a technical, creative, and organizational perspective. We’ll analyze content, writing style, visual design, and interface design, and make sure we understand everything there is to know about your industry. Our project analysis will guide us in understanding where your organization has been, what it is currently doing, and where it wants to go in the future. This guides us in tailoring a solution that is effective and sustainable. We will also spend time getting to really understand your brand by analyzing past and present marketing materials, discussing future marketing strategies, and aligning them with your web project.

Slide 28

Slide 28 text

Project Analysis We will work with you to help determine the requirements of the project, from a technical, creative, and organizational perspective. We’ll analyze content, writing style, visual design, and interface design, and make sure we understand everything there is to know about your industry. Our project analysis will guide us in understanding where your organization has been, what it is currently doing, and where it wants to go in the future. This guides us in tailoring a solution that is effective and sustainable. We will also spend time getting to really understand your brand by analyzing past and present marketing materials, discussing future marketing strategies, and aligning them with your web project.

Slide 29

Slide 29 text

Personas, audience proﬁles

Slide 30

Slide 30 text

Using the knowledge gained from our discovery conversations, we will audit existing content both quantitatively and qualitatively. What exists on your current site? And, more importantly, is it doing what you need it to do? We'll create a site map for your project and show where everything belongs. This process will inform what and how we communicate, and establish the features your users need. Well-planned, well-structured content will help us create both the interaction and visual design systems.

Slide 31

Slide 31 text

www.gathercontent.com • Quantitative audit • Qualitative audit • Card sort • High level site map • Gap analysis • User stories

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

Headed down the right track. All of the information found during the discovery phase will be complied into a concise document that outlines the search, content, technical, and creative strategies. This document will act as the project map, keeping all team members in line with a focused strategy.

Slide 34

Slide 34 text

Design. From sketching to in-browser designs to documentation and everything in between.

Slide 35

Slide 35 text

http://youtu.be/8m9EVP8X7N8 http://www.youtube.com/watch?v=8m9EVP8X7N8

Slide 36

Slide 36 text

http://youtu.be/bVnfyradCPY UX sketch or paper prototype! http://www.commoncraft.com/video/ zombies

Slide 37

Slide 37 text

We will work with you through an iterative process to create rough wireframes, or UX sketches, for key views. This will help establish the design system, while communicating a sense of the functionality. This is also where we decide on the break points for the responsive design.

Slide 38

Slide 38 text

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

http://appsketchbook.com/products/responsive-design-sketchbook

Slide 41

Slide 41 text

One of our main goals is to keep content independent from design or presentation. Your content should never be dependent on a layout to work properly. So, along with wireframes, you will receive a set of page tables for key content pages. Page tables identify each content area in priority order, and identify the most important messages to communicate in each area.

Slide 42

Slide 42 text

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

Once we all agree on where we’re headed, we’ll wireframe and document the remaining views, with the functionalities established by the page tables and feature list. Each and every view scenario will be documented to visualize all the content and features we’ve planned. Along with that we’ll create rough greybox HTML prototypes to demonstrate responsive interaction patterns.

Slide 45

Slide 45 text

http://responsiveprocess.com/yp2012/wireframes/

Slide 46

Slide 46 text

http://twitter.github.com/bootstrap

Slide 47

Slide 47 text

http://foundation.zurb.com/

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

BADASS ICONS

Slide 50

Slide 50 text

With functionality fully documented in the wireframes, we’ll layer in the branding elements, colour palettes, and typography that give each site its unique look and feel. Through an iterative process between our team and yours, we’ll make all the big decisions about typographic hierarchy, vertical rhythm, and interface details. We can create static visual mockups, browser-based prototypes, or both.

Slide 51

Slide 51 text

Get it in the browser!

Slide 52

Slide 52 text

http://styletil.es

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

Next, we’ll create a styleguide that will document the design system so that they can be properly implemented. All the details from the grid to hover/touch states to typography styles to content messaging will be detailed. This guide will demonstrate the design thinking and personality of the system. Depending on the complexity of the site, this could be created in an interface harmony canvas.

Slide 57

Slide 57 text

Text http://nathanborror.com/posts/2009/oct/25/interface-harmony/ An interface harmony canvas

Slide 58

Slide 58 text

Development

Slide 59

Slide 59 text

http://www.sonypictures.com/previews/movies/residentevilretribution/clips/4301/ The developers Zombie movie

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

Now it’s time to get down to business and build HTML/CSS/JavaScript themes: functional, browser-tested, HTML pages ready for testing. We’ll make sure all content is governed by CSS and meets W3C standards. We’ll use JavaScript for interactive elements, rather than Flash or Silverlight. We’ll also help you adhere to best practices for online readability, and include a print CSS for readers that want to print out your content.

Slide 62

Slide 62 text

No content

Slide 63

Slide 63 text

At this stage, the technical architecture will be built out on a system like Open Text Web Site Management or Drupal 7, depending on your organization’s needs. We’ll build out all of the site’s modular elements and e-commerce components, and set up a workflow process that will help you maintain your content over the long term. This process goes hand-in-hand with the CMS Template Implementation, which will integrate the HTML templates into the design or theme layer. By the time we’re done, everything will be looking good and working great!

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

Here's where we test and demonstrate how page templates will render in major web browsers and mobile devices (i.e. iPad, iPhone, Blackberry, Android, etc). It is important to understand that the design will be appropriate for each device, but may be slightly different due to device specs and experience. It’s not about making everything look the same, it’s about creating a coherent experience across all devices.

Slide 66

Slide 66 text

Slide 67

Slide 67 text

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

Slide 68

Slide 68 text

Oh noes!

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

www.adobe.com/Shadow Testing devices through adobe shadow!

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

Deployment

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

At Yellow Pencil we love to provide support and training for content authors during content migration. We believe in helping our clients create and maintain useful, usable content. Depending on your organization’s needs, and our audit of your current website, we’ll help you define the scope of the content migration phase. As we all know, a website without content is a black hole of sadness. Content #FTW!

Slide 75

Slide 75 text

Slide 76

Slide 76 text

User Acceptance Testing (UAT) helps us confirm that your new site meets the objectives and requirements we defined early in the project. It's like moving into a new house – you need time to discover how everything works and get comfortable with living there. You’ll need time to come to terms with how your content fits into the design and workflow, and make any adjustments and edits you need.

Slide 77

Slide 77 text

http://youtu.be/yfDUv3ZjH2k Sometimes things don’t turn out how you think they will. http://youtu.be/ yfDUv3ZjH2k (that’s not exactly like 28 Days Later)

Slide 78

Slide 78 text

Wasn’t this supposed to look like a normal zombie movie...

Slide 79

Slide 79 text

Documentation & Training

Slide 80

Slide 80 text

Document the patterns and systems we’ve established!

Slide 81

Slide 81 text

Launch Plan & Release

Slide 82

Slide 82 text

Where is it being hosted? Level of support? Who will know about this? How will you communicate with current users?

Slide 83

Slide 83 text

We need to get this digital thing into the real world.

Slide 84

Slide 84 text

Start of Operational Plan

Slide 85

Slide 85 text

This is where the web project really starts its life. Celebrate the birth and plan to celebrate every milestone as it lives.

Slide 86

Slide 86 text

No content

Slide 87

Slide 87 text

Move from the inside out. Extrinsic vs intrinsic motivation.

Slide 88

Slide 88 text

Brings me to the question of what drives us? Extrinsic vs intrinsic. Is it a motivation 2.0 or 3.0 thing? People don’t believe in what you do, they believe in why you do it. These were just some examples. What will your aha! moment be?

Slide 89

Slide 89 text

No content

Slide 90

Slide 90 text

vimeo.com/29180214

Slide 91

Slide 91 text

vimeo.com/15266890

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

No content

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

No content

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

No content

Slide 101

Slide 101 text

No content

Slide 102

Slide 102 text

vimeo.com/15266890

Slide 103

Slide 103 text

What = undead

Slide 104

Slide 104 text

What = surrounded and losing hope

Slide 105

Slide 105 text

What = alone

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

No content

Slide 108

Slide 108 text

How = taking care of business

Slide 109

Slide 109 text

How = killing the brain to save the living

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

Why = remaining human in the face of it all.

Slide 112

Slide 112 text

We focus on features and devices but that’s not right.

Slide 113

Slide 113 text

The web isn’t a bunch of machines. It is a bunch of humans.

Slide 114

Slide 114 text

No content

Slide 115

Slide 115 text

No content

Slide 116

Slide 116 text

No content

Slide 117

Slide 117 text

No content

Slide 118

Slide 118 text

We need to remember that each connection on the web is a connection with another human. We are trying to become wholehearted

Slide 119

Slide 119 text

This is why I love RWD. It is about helping people connect on the web.

Slide 120

Slide 120 text

No content

Slide 121

Slide 121 text

Our why = helping everyone be able to connect with and use the web

Slide 122

Slide 122 text

No content

Slide 123

Slide 123 text

No content

Slide 124

Slide 124 text

No content

Slide 125

Slide 125 text

No content

Slide 126

Slide 126 text

No content

Slide 127

Slide 127 text

No content

Slide 128

Slide 128 text

No content

Slide 129

Slide 129 text

No content

Slide 130

Slide 130 text

No content

Slide 131

Slide 131 text

No content

Slide 132

Slide 132 text

Focus on the why, well structured content, and interactions that matter

Slide 133

Slide 133 text

So what does it mean to be responsive? Something simple?

Slide 134

Slide 134 text

It is about good content. It means rethinking content creation. Moving from fragmentation to uniﬁcation!

Slide 135

Slide 135 text

create once publish everywhere

Slide 136

Slide 136 text

We want our data to tell stories and we can’t predict what future devices or interactions will be.