/
index.html
317 lines (273 loc) · 12 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6" lang="en"> <![endif]-->
<!--[if IE 7]> <html class="no-js ie7" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="no-js ie8" lang="en"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en"> <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Responsive Design in Knowledge & Learning</title>
<meta name="description" content="A presentation about how we intend to deliver a responsive application in KandL. Delivered at Team Brief on 13th July 2012">
<meta name="author" content="Ryan Adams">
<meta name="viewport" content="width=1024, user-scalable=no">
<!-- Core and extension CSS files -->
<link rel="stylesheet" href="deck.js/core/deck.core.css">
<link rel="stylesheet" href="deck.js/extensions/goto/deck.goto.css">
<link rel="stylesheet" href="deck.js/extensions/menu/deck.menu.css">
<link rel="stylesheet" href="deck.js/extensions/navigation/deck.navigation.css">
<link rel="stylesheet" href="deck.js/extensions/status/deck.status.css">
<link rel="stylesheet" href="deck.js/extensions/hash/deck.hash.css">
<link rel="stylesheet" href="deck.js/extensions/scale/deck.scale.css">
<link rel="stylesheet" href="assets/style.css">
<!-- Style theme. More available in /themes/style/ or create your own. -->
<link rel="stylesheet" href="deck.js/themes/style/web-2.0.css">
<!-- Transition theme. More available in /themes/transition/ or create your own. -->
<link rel="stylesheet" href="deck.js/themes/transition/horizontal-slide.css">
<script src="deck.js/modernizr.custom.js"></script>
</head>
<body class="deck-container">
<!-- Begin slides -->
<section class="slide" id="title-slide">
<h1>Responsive Design in Knowledge & Learning</h1>
<p>by Ryan Adams <a href="mailto:ryan.adams@bbc.co.uk">ryan.adams@bbc.co.uk</a></p>
</section>
<section class="slide" id="mobile-first">
<h2>What is Responsive Design?</h2>
<blockquote>
<p>as a general rule; let's design/wireframe for mobile first this time round? (yes, responsive design, etc etc)</p>
<p><cite>Chris Sizemore</cite></p>
</blockquote>
</section>
<section class="slide" id="what-is-responsive-design">
<h2>What is Responsive Design?</h2>
<blockquote>
<p>any approach that delivers elegant visual experiences regardless of the size of the user’s display and the limitations or capabilities of the device</p>
<p><cite>Jeffrey Zeldman
<a href="http://bit.ly/zeldman_responsive">http://bit.ly/zeldman_responsive</a></cite></p>
</blockquote>
</section>
<section class="slide" id="what-is-responsive-technical">
<h2>What is Responsive Design?</h2>
<blockquote><p>
Delivering the same features of a product, optimised for each device, to all devices at the same time, using the same codebase.</p>
<p><cite>Ryan Adams</cite></p>
</blockquote>
</section>
<section class="slide" id="today">
<h2>The standard approach</h2>
<div id="today-desktop" style="width:50%;float:left;">
<h2>desktop</h2>
<img src="assets/bbc-homepage-2012.png" />
<ul>
<li>http://www.bbc.co.uk</li>
<li>About 650KB page weight</li>
<li>92 http requests</li>
</ul>
</div>
<div id="today-mobile" style="width:50%;float:left;">
<h2>mobile</h2>
<img src="assets/bbc-homepage-mobile-2012.png" />
<ul>
<li>http://m.bbc.co.uk</li>
<li>130KB page weight</li>
<li>16 requests</li>
</ul>
</div>
</section>
<!--
Device Detection, but UA string isn't everything
Needs to be on the server side, therefore requires m.bbc or a different url
-->
<section class="slide" id="android-sizes">
<h2>Mobile?</h2>
<img src="assets/android-variants1.png">
<pre><a href="http://stephanierieger.com/the-trouble-with-android/">http://stephanierieger.com/the-trouble-with-android/</a></pre>
</section>
<section class="slide" id="browser-support">
<h2>Browser Support</h2>
<img src="assets/browser-stats-top.png">
<pre>+375 others</pre>
</section>
<section class="slide" id="support-table">
<h2>BBC Browser Support Table</h2>
<table summary="Browser support and test levels" class="browserTable">
<thead>
<tr>
<th>Browser</th>
<th><abbr title="Internet Explorer">IE</abbr></th>
<th><abbr title="Firefox">FF<sup>1</sup></abbr></th>
<th>Chrome<sup>2</sup></th>
<th>Opera<sup>1</sup></th>
<th>Safari<sup>1</sup></th>
<th>Konqueror</th>
</tr>
<tr class="subHead">
<th>Platform</th>
<th>Windows</th>
<th>All</th>
<th>Windows & Mac</th>
<th>All</th>
<th>All</th>
<th>Linux</th>
</tr>
</thead>
<tbody>
<tr class="level1">
<th>Level 1</th>
<td>6, 7, 8</td>
<td><abbr title="Mozilla"></abbr><abbr title="Firefox">FF</abbr> 4.0.x, 3.6.x, 3.5.x, 3.0.x</td>
<td><em>latest x.x</em></td>
<td>10.x, 9.6.x, 9.5.x</td>
<td>5.x, 4.x, 3.x</td>
<td> </td>
</tr>
<tr class="level2">
<th>Level 2</th>
<td>5.5</td>
<td>FF 2.0.x</td>
<td> </td>
<td>9.x</td>
<td>2.x (Mac)</td>
<td>4.4x</td>
</tr>
<tr class="level3">
<th>Level 3</th>
<td>1, 2, 3, 4, 5</td>
<td><abbr title="Mozilla Firefox">FF 1.5.x</abbr>, 1.0.x</td>
<td> </td>
<td>8-</td>
<td>1.x (Mac)</td>
<td>3-</td>
</tr>
<tr>
<th>Must test</th>
<td>6, 7, 8</td>
<td>FF 3.6.3<br>
(PC Only)</td>
<td><em>latest x.x</em><sup>1</sup></td>
<td>10.53 (PC)</td>
<td>5.0 (Mac, 4.0.3 (Mac)</td>
<td> </td>
</tr>
<tr>
<th>Should test</th>
<td>5.5</td>
<td>FF 3.0.6 (Mac), 3.5.7 (PC)</td>
<td> </td>
<td style="width:6em">9.52, 9.64</td>
<td>3.2.1 (PC), 3.2.1 (Mac)</td>
<td> </td>
</tr>
<tr>
<th>Engine</th>
<td>Trident (4-7), Ohare (1-3)</td>
<td>Gecko</td>
<td>Webkit</td>
<td>Presto</td>
<td>Webcore</td>
<td>KHTML</td>
</tr>
</tbody>
</table>
<p> </p>
<pre><a href="http://www.bbc.co.uk/guidelines/futuremedia/technical/browser_support.shtml">http://www.bbc.co.uk/guidelines/futuremedia/technical/browser_support.shtml</a></pre>
</section>
<section class="slide" id="browser-support-two">
<h2>Browser Support</h2>
<blockquote>
A year from now, the most popular ‘browser’ may just be be the embedded web view full of ‘related’ links in a Stephen King iBooks bestseller.
<p><cite><a href="http://stephanierieger.com/viewports-all-the-way-down/">http://stephanierieger.com/viewports-all-the-way-down/</a></cite></p>
</blockquote>
</section>
<section class="slide" id="browser-support-statement">
<h1>We will support all browsers, but we won't treat them all the same.</h1>
</section>
<section class="slide" id="but-how">
<h2>But How?</h2>
<ul>
<li class="slide"><h3>CSS media queries</h3>
<pre><code>@media screen and (max-width: 400px) {
body { color: red; }
}</code></pre>
</li>
<li class="slide"><h3>Cutting the Mustard™</h3>
<pre><code>
if ('querySelector' in document &&
'addEventListener' in window &&
'localstorage' in window ) {
console.log("I can cut mustard");
}</code>
<a href="http://blog.responsivenews.co.uk/post/18948466399/cutting-the-mustard">http://blog.responsivenews.co.uk/post/18948466399/cutting-the-mustard</a></pre></li>
<li class="slide"><h3>Browser based page assembly</h3>
<blockquote class="twitter-tweet" data-in-reply-to="180418345550610432"><p>@<a href="https://twitter.com/ryangadams">ryangadams</a> the future is not gluing applications together in php. build a massive JS application instead. server = data.</p>— Matt Chadburn (@commuterjoy) <a href="https://twitter.com/commuterjoy/status/180420447047913473" data-datetime="2012-03-15T22:29:21+00:00">March 15, 2012</a></blockquote>
<script src="//platform.twitter.com/widgets.js" charset="utf-8"></script></li>
</ul>
</section>
<section class="slide" id="graded-browser-grid">
<h2>We will support all browsers.</h2>
<img src="https://confluence.dev.bbc.co.uk/download/attachments/49920198/Browser+Support+Grid.png?version=1&modificationDate=1338461740000">
</section>
<!--
<section class="slide" id="application-design-speed">
<h2>Web Application Design</h2>
<blockquote class="twitter-tweet"><p>Is it reasonable to make speed the number 1 priority of web application design?</p>— Ryan Adams (@ryangadams) <a href="https://twitter.com/ryangadams/status/184284837748817920" data-datetime="2012-03-26T14:25:03+00:00">March 26, 2012</a></blockquote>
<script src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
<blockquote class="twitter-tweet" data-in-reply-to="184284837748817920"><p>@<a href="https://twitter.com/ryangadams">ryangadams</a> yes. speed over features.</p>— Matt Chadburn (@commuterjoy) <a href="https://twitter.com/commuterjoy/status/184295980118720512" data-datetime="2012-03-26T15:09:20+00:00">March 26, 2012</a></blockquote>
<script src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
</section>
-->
<section class="slide" id="prototyping">
<h2>Responsive Prototyping</h2>
<pre><a href="http://www.int.bbc.co.uk/responsivefood/">food homepage</a>
<a href="http://www.int.bbc.co.uk/responsivefood/recipes">recipe</a>
<a href="http://www.int.bbc.co.uk/jsassembler/">modular</a></pre>
</section>
<section class="slide" id="prototype-learnings">
<h2>What we learned</h2>
<ul>
<li>Homepages are hard</li>
<li>Need to think about mobile & desktop at the same time</li>
<li>Javascript behaviours that depend on layout are tricky</li>
<li>Media elements need careful consideration - video, images</li>
</ul>
</section>
<section class="slide" id="whats-next">
<h1>?</h1>
</section>
<!-- deck.navigation snippet -->
<a href="#" class="deck-prev-link" title="Previous">←</a>
<a href="#" class="deck-next-link" title="Next">→</a>
<!-- deck.status snippet -->
<p class="deck-status">
<span class="deck-status-current"></span>
/
<span class="deck-status-total"></span>
</p>
<!-- deck.goto snippet -->
<form action="." method="get" class="goto-form">
<label for="goto-slide">Go to slide:</label>
<input type="text" name="slidenum" id="goto-slide" list="goto-datalist">
<datalist id="goto-datalist"></datalist>
<input type="submit" value="Go">
</form>
<!-- deck.hash snippet -->
<a href="." title="Permalink to this slide" class="deck-permalink">#</a>
<!-- Grab CDN jQuery, with a protocol relative URL; fall back to local if offline -->
<script src="//ajax.aspnetcdn.com/ajax/jQuery/jquery-1.7.min.js"></script>
<script>window.jQuery || document.write('<script src="deck.js/jquery-1.7.min.js"><\/script>')</script>
<!-- Deck Core and extensions -->
<script src="deck.js/core/deck.core.js"></script>
<script src="deck.js/extensions/hash/deck.hash.js"></script>
<script src="deck.js/extensions/menu/deck.menu.js"></script>
<script src="deck.js/extensions/goto/deck.goto.js"></script>
<script src="deck.js/extensions/status/deck.status.js"></script>
<script src="deck.js/extensions/navigation/deck.navigation.js"></script>
<script src="deck.js/extensions/scale/deck.scale.js"></script>
<!-- Initialize the deck -->
<script>
$(function() {
$.deck('.slide');
});
</script>
</body>
</html>