{"id":110,"date":"2013-03-11T03:30:17","date_gmt":"2013-03-10T17:30:17","guid":{"rendered":"http:\/\/www.jasonshanks.com\/?p=110"},"modified":"2013-03-14T15:27:25","modified_gmt":"2013-03-14T05:27:25","slug":"wk-3tut-2-responsive-web-design-part-1","status":"publish","type":"post","link":"https:\/\/www.jasonshanks.com\/2013\/lectures-and-tuts\/kib204-web_interface_design\/wk-3tut-2-responsive-web-design-part-1\/","title":{"rendered":"Wk 3\/Tut 2 : Responsive Web Design – Part 1"},"content":{"rendered":"
Responsive Web Design is a term initially coined by web designer\/developer Ethan Marcotte<\/a>. It is now a W3C Candidate Recommendation<\/a>, ready to be implemented by all modern browser vendors. Following on from support in CSS2 for different media types such as screen<\/strong> and print<\/strong>, it essentially a set of additional media types based mostly on width<\/strong> (or not as widely used height<\/strong>). It could also be considered a subset of a more far-reaching movement called Progressive enhancement<\/a> \u2013 in which all content is designed to gracefully degrade to the lowest common denominator.<\/p>\n Luke Wroblewski, author of Mobile First<\/a>, writes and speaks extensively on the subject. In this<\/a> article he gives an excellent run down of the progression of responsiveness in approaches.<\/p>\n Rather than target specific devices, a current list of which would change monthly these days, the general idea is that you consider typical screen widths and at which points to alter your content.<\/p>\n As you set up your Media Queries you must take your actual content into consideration and subjectively apply that to a loose current understanding of where the majority of devices fall in perceived<\/em> screen dimensions. For instance the iPad with Retina display reches 2048×1536 pixels or 264ppi, however that is an exact doubling of 1024×768 at which content designed for those dimensions will appear completely normal as the iPad intuitively zooms in 200%.<\/p>\n For instance, at the most basic level one could set up a break point right above the size of most smartphones:<\/p>\n For more advanced possibilities check out these articles:<\/p>\n Brad Frost has a great collection of common implementations<\/a>.<\/p>\n Responsive Data Table Roundup<\/a><\/p>\n It’s best practice these days to use a fixed Base font size and relative proportions to this for every other declared size. This can be done through either:<\/p>\n Here are 2 examples of free online tools to help with your calculations:<\/p>\nProgression of Responsive Approaches<\/h2>\n
Mostly Fluid<\/h4>\n
\n
Column Drop<\/h4>\n
\n
Layout Shifter<\/h4>\n
\n
Tiny Tweaks<\/h4>\n
\n
Off Canvas<\/h4>\n
\n
Choosing Break Points (targeting ranges of or addressing specific Viewports)<\/h2>\n
@media (min-width: 500px){\/*selectors*\/{\/*properties*}}\r\n@media (max-width: 499px){\/*selectors*\/{\/*properties*}}\r\n<\/code><\/pre>\n
\n
What do you do with the Navigation Menu?<\/h2>\n
What do you do with Tables?<\/h2>\n
Other RWD Resources<\/h2>\n
Examples:<\/h3>\n
\n
Articles:<\/h3>\n
\n
Boilerplates:<\/h3>\n
\n
Flexible Fonts:<\/h3>\n
\n
\n
Responsive Testing:<\/h3>\n
\n
\nResponsive Design Exercise – Part 1<\/h2>\n