Responsive Web Design Process
17 likes3,914 views
This document appears to be a presentation about responsive web design and the web design process. It begins by introducing the speaker and provides some background information. It then outlines the key steps in a responsive web design process, including discovery, information architecture, wireframing, visual design, development, testing, content migration, launch, and ongoing support. Interactive examples and references are provided throughout to illustrate concepts. The overall message is about having a well-structured, iterative process to create responsive websites that meet user needs across devices.
Responsive Web Design Process
- 2. Twitter = @hellofisher Web = www.hellofisher.com / www.yellowpencil.com
- 3. I’m Canadian delicious.com/ hellofisher
- 4. HOCKEY!
- 5. I’m not going to talk about html5, css3, & that stuff Going to talk about the process.
- 6. But I’m still a giant nerd Going to talk about the process.
- 7. Well... maybe a little html Going to talk about the process.
- 8. CSS3! HTML5! Going to talk about the process.
- 10. I’m a UX Designer I’m special!
- 11. I’m super smart This is what I think about what I do! I mean come on! I make the web a better place!
- 12. What? This is what almost everyone else thinks. You’re a what?
- 13. How about this? Well how about this...
- 14. @themaninblue - http://www.themaninblue.com/writing/perspective/2008/08/12/ Crossing the border, etc.
- 15. Ah ha! Ah ha! It all makes sense now!
- 18. The web is not fixed width.
- 21. 28 Days Later http://youtu.be/eunaclr-WgU - Zombie movie trailer (getting to know the baseline story)
- 22. 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.
- 23. You want to know who you are working with... Project planner
- 24. 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.
- 26. 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.
- 27. www.gathercontent.com • Quantitative audit • Qualitative audit • Card sort • High level site map • Gap analysis • User stories
- 28. 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.
- 30. From sketching to in-browser designs to documentation and everything in between.
- 31. Zombieland Trailer http://www.youtube.com/watch?v=8m9EVP8X7N8 - High fidelity prototype or in-browser design!
- 32. UX sketch or paper prototype! http://www.commoncraft.com/video/zombies
- 33. 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.
- 35. 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.
- 37. 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.
- 39. 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.
- 40. Get it in the browser!
- 41. 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.
- 44. The developers zombie movie http://www.sonypictures.com/previews/movies/ residentevilretribution/clips/4301/
- 45. 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.
- 47. 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!
- 48. 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.
- 49. 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.
- 52. 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!
- 53. 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.
- 54. Sometimes things don’t turn out how you think they will. http://youtu.be/yfDUv3ZjH2k (that’s not exactly like 28 Days Later)
- 55. Wasn’t this supposed to look like a normal zombie movie...
- 56. We will prepare text and video documentation on to help you understand and use your new CMS and site. We will generally provide a period of user acceptance testing following the official “handoff” of the website, to make absolutely sure that everything meets your needs. We’ll also provide additional support and training where necessary, and take care of any bug fixes to make sure that your website is ready for launch.
- 58. So close! Next up, our team will create a launch plan to archive the current website (if needed) and release the new website to the public, as well as a quality checklist to ensure that all project requirements are met. We’ll make sure that the new website is submitted to the appropriate search engines, and that web analytics are installed and configured. We'll also work with our smarty-pants friend at the Status Bureau to make sure you understand how to access and act on web analytics reports.
- 59. A website is a living thing that continues to grow and change throughout its lifecycle. So in some ways, your work is never done (sorry), but achieving a milestone like this definitely deserves a party! Even though this is just the beginning of the real life of the website, it’s good to celebrate after all this hard work. Nice work team. Now back to work!
- 60. It’s a celebration of life!
- 61. BUT I WANT TO EAT THE ICING NOW!!
- 62. This is what happens when you skip ahead and don’t follow the process.
- 63. Focus on the why well structured content and interactions that matter
- 64. What does it mean to be responsive?
- 65. Something Simple? One web concepts really tie things together. Rather than multiple sites there is just one.
- 68. Move from the inside out. Extrinsic vs intrinsic motivation. I want the world to be able to publish their knowledge freely. I’ll create a distributed code base that anyone can use. It will be a CMS called Drupal.
- 69. 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?
- 70. The future?
- 71. The first website was RESPONSIVE! Surprise! :P
- 72. A responsive process is a responsible process
- 74. Just because. Thriller! http://www.youtube.com/watch?v=hG6oy46qKE4
Editor's Notes
- #2: Check out www.responsiveprocess.com\n
- #3: Twitter = @hellofisher\nWeb = www.hellofisher.com / www.yellowpencil.com\n
- #4: \n
- #5: \n
- #6: Going to talk about the process.\n
- #7: Going to talk about the process.\n
- #8: Going to talk about the process.\n
- #9: Going to talk about the process.\n
- #10: On my own.\n
- #11: I’m special!\n
- #12: This is what I think about what I do! I mean come on! I make the web a better place!\n
- #13: This is what almost everyone else thinks. You’re a what?\n
- #14: Well how about this...\n
- #15: Crossing the border, etc.\n
- #16: Ah ha! It all makes sense now!\n
- #17: Poor Steve\n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: 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.\n
- #24: You want to know who you are working with...\nProject planner\n
- #25: 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.\n
- #26: Personas, audience profiles\n\n
- #27: 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.\n\n\n
- #28: Quantitative audit\nQualitative audit\nCard sort\nHigh level site map\nGap analysis\nUser stories\n
- #29: 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.\n
- #30: \n
- #31: From sketching to in-browser designs to documentation and everything in between.\n
- #32: High fidelity prototype or in-browser design!\n
- #33: UX sketch or paper prototype!\n
- #34: 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.\n
- #35: http://appsketchbook.com/products/responsive-design-sketchbook\n
- #36: 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.\n
- #37: \n
- #38: 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.\n
- #39: \n
- #40: 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.\n
- #41: Get it in the browser!\n
- #42: 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.\n
- #43: http://nathanborror.com/posts/2009/oct/25/interface-harmony/\n
- #44: \n
- #45: \n
- #46: 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.\n
- #47: \n
- #48: 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!\n
- #49: 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.\n
- #50: 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.\n
- #51: \n
- #52: \n
- #53: 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!\n
- #54: 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.\n
- #55: \n
- #56: Wasn’t this supposed to look like a normal zombie movie...\n
- #57: We will prepare text and video documentation on to help you understand and use your new CMS and site. We will generally provide a period of user acceptance testing following the official “handoff” of the website, to make absolutely sure that everything meets your needs. We’ll also provide additional support and training where necessary, and take care of any bug fixes to make sure that your website is ready for launch.\n
- #58: \n
- #59: So close! Next up, our team will create a launch plan to archive the current website (if needed) and release the new website to the public, as well as a quality checklist to ensure that all project requirements are met. We’ll make sure that the new website is submitted to the appropriate search engines, and that web analytics are installed and configured. We'll also work with our smarty-pants friend at the Status Bureau to make sure you understand how to access and act on web analytics reports.\n
- #60: A website is a living thing that continues to grow and change throughout its lifecycle. So in some ways, your work is never done (sorry), but achieving a milestone like this definitely deserves a party! Even though this is just the beginning of the real life of the website, it’s good to celebrate after all this hard work. Nice work team. Now back to work!\n
- #61: It’s a celebration of life!\n
- #62: \n
- #63: This is what happens when you skip ahead and don’t follow the process.\n
- #64: \n
- #65: \n
- #66: One web concepts really tie things together. Rather than multiple sites there is just one.\n
- #67: \n
- #68: \n
- #69: Move from the inside out. Extrinsic vs intrinsic motivation. I want the world to be able to publish their knowledge freely. I’ll create a distributed code base that anyone can use. It will be a CMS called Drupal.\n
- #70: Brings me to the question of what drives us? Extrinsic vs intrinsic. Is it a motivation 2.0 or 3.0 thing?\nPeople don’t believe in what you do, they believe in why you do it.\n\nThese were just some examples. What will your aha! moment be?\n
- #71: \n
- #72: The first website was RESPONSIVE! Surprise! :P\n
- #73: \n
- #74: \n
- #75: \n
- #76: \n