Format: PDF / Kindle (mobi) / ePub
Responsive design is more than the technical; it’s a new way of communicating and working that affects every person on your team. Karen McGrane draws on data and stories from real-world teams to show you why going responsive is just good business sense—and how to set up your project (from concept to launch) for total success. Learn how to plan and scope work, collaborate in a responsive context, evaluate content, handle browser support and testing, and measure performance outcomes. No matter your role or project, go responsive with confidence.
replatforming the CMS. For many websites, a retrofit also helps mitigate political concerns around changing or damaging the desktop experience, since it doesn’t change much. Here’s how you roll out a retrofit right: “Don’t touch the desktop” is a mandate often handed down to the responsive team, but this guideline is too limiting. It forces the team to work toward unnecessary design parity at the expense of making better design decisions for smaller screens. “Do no harm to the desktop” is a
jointly responsible for the same objective: a working website” (http://bkaprt.com/gr/02-10/). When designers and developers sit on different teams and report to different people, they’re motivated by different goals and expectations. Aligning everyone may need to happen at higher levels of the org chart. Even if design and development teams remain as separate groups, managers must train teams and facilitate a much higher degree of collaboration. Jason Chandler, Manager, Client Side Engineering
on top of each other, but that doesn’t preserve the intended prioritization of objects. Content choreography ensures that the visual hierarchy makes sense as items shift between different breakpoints (http://bkaprt.com/gr/04-08/). Paravel founder Trent Walton coined the phrase “content choreography” to describe the process of stacking or grouping elements across different screen widths (http://bkaprt.com/gr/04-07/). Managing these “in-between states” lies at the heart of a responsive design
05-06 http://bohemiancoding.com/sketch/ 05-07 http://macaw.co/ 05-08 http://www.invisionapp.com/ 05-09 https://creative.adobe.com/products/reflow 05-10 http://twitter.github.com/bootstrap/ 05-11 http://foundation.zurb.com/ 05-12 http://gumbyframework.com/ 05-13 http://www.getskeleton.com/ 05-14 https://the-pastry-box-project.net/dan-mall/2012-september-12 05-15 http://alistapart.com/article/language-of-modular-design 05-16 http://responsivewebdesign.com/podcast/code-for-america.html
Companies can outsource or temporarily expand their teams to build things in parallel, which isn’t free, but when the money dries up you’ll have twice or thrice the amount of code to maintain and extend, which also isn’t free or sustainable. You’ll be chasing your tail whatever you pick unless you’ve got enough developers to build and maintain a few versions of everything (http://bkaprt.com/gr/01-22/). By shifting to a responsive design, a single unified team can work together to build a single