Responsive design "frees our content" to work anywhere, anytime. Adopting responsive design means that technical communicators no longer need to spend time designing and creating deliverables for different devices. Instead, we can focus on developing and delivering quality content – where and when our customers need it.
Technically, responsive design is "Responsive WEB design", so we must deliver our help to the web to take advantage of all that RWD has to offer. But this is nothing new for technical communicators, since many of us have been delivering web based help systems for many years, and mobile help for a shorter time. Providing a single responsive output gives us the opportunity to create once and deliver to thousands of devices: new ones, older ones – and ones that don’t even exist yet.
In this talk, you’ll learn: What responsive design is. * How responsive design works; a short primer. (Content stacking and the technology behind it —media queries, fluid layouts, flexible images ― so everyone is familiar with the terminology and technologies.) * Five reasons to consider responsive design (besides the flexibility). * Nine “mobile first” content development best practices for technical communicators. (Because when you write/make other changes for mobile, then the content will work well on tablets, the desktop, etc.) * Where to find examples of responsive designs, as well as responsive design resources.