1. Responsive Web Design Nuts & Bolts David Weedon - UI/UX Designer, Covenant Technology Partners

2. Responsive Web Design the bee’s knees

3. Rapidly taking over the web. Easy to learn. Focus on good design.

4. Show and Tell thesearethings.com smashingmagazine.com foodsense.is

5. What works. Intelligent, content driven adjustments Keeping content consistent Consider mobile motives when adjusting navigation and calls to action.

6. What doesn't. Hiding content that doesn’t fit. Adjusting content to fit on popular devices. Bloat. Ignoring context.

7. Content First. Please.

9. Why content first? RWD eats up a lot of time up front. Redesigns to fit unexpected content is costly. Don’t try to fit circle content into square design.

10. Why content first? Good Design is tailored to the content. Book covers before books? Design before content is like using a template. Good content is good, regardless of the design.

11. How it’s done. @media

12. CSS3’s Media Query

13. Where should they be set. It really depends. Don’t use popular device widths. Break it when it breaks.

14. Inclusive: Inherited Styles

15. Exclusive: Isolated Styles

16. Min and Max Width In general try to keep it going in one direction. Use mostly min or mostly max width media queries. Use Exclusive queries to block out drastically different styles.

17. That one direction should be up. (Mobile First)

18. Don’t forget paper!

19. Retina… Generally more work than other types of media queries because it generally requires additional content.

20. The hard way: For tags, just use retina.js or use SVG, an icon font, or css3.

21. The easy way: Don’t use images for your UI. Use CSS3 and icon fonts.

22. Living on the grid.

23. Good design tends to happen in a grid The Saccadic Reflex Mathematical (or at least proportional) design. x-height, golden mean, rhythmic typography

26. Not possible. Responsive design changes only the CSS. You can’t change classes. You can change how a class acts, but then you have a “hackish,” “unsemantic” approach.

27. big CSS.

28. RWD starts to be a lot of CSS really fast. Too much to keep track of. Lots of overwriting when using grids. Small changes means potentially changing many styles.

29. CSS pre-processers to the rescue! SASS and LESS

30. Sass and Less mostly do the same thing. Very similar features, slightly different syntax. Great for any css project, even small ones. They are just faster.

31. SCSS or Sassy CSS: variables

32. SCSS or Sassy CSS: Include

33. SCSS or Sassy CSS: Mixin

34. SCSS or Sassy CSS: Functions

35. So… back to our grid problem.

36. Remembering Our Past or: How I Learned to Stop Worrying and Love IE8

37. All this CSS3 stuff is great… but: I need to support IE8 :’(

38. Sass Media Query Mixin + Sass Global Variable + IE conditional comments IE8 stylesheet with only desktop styles

39. CSS3 PIE Almost as good as real pie.

40. PIE uses javascript to simulate CSS3 properties. Time and bandwidth saved. No more image based gradients, rounded corners, or box-shadows.

41. Work smart. Not hard. There are some fantastic Sass, LESS, and general responsive frameworks available.

42. Compass (think: jQuery for CSS), Semantic.gs, Gumby, Skeleton, Bootstrap, Etc.

43. Bringing to SharePoint. via SharePoint Designer

44. SharePoint has a lot of built in structure. Important to understand what SharePoint is going to give you. Get the snippits that you will need before writing your HTML

47. For most things on a simple page or site-collection, no.NET experience is required. However, sometimes you really just need a developer.

48. Device Channels Better than RWD?

49. Actually, yes. In terms of robustness, device channels can do everything RWD can and more. RWD only changes the way the HTML is displayed, Device Channels allow for separate HTML.

50. Device channels require more work. Are harder to maintain. Limited to publishing pages. Mix the two: HTML handled by device channels and CSS handled by RWD?

51. Case Study: STLSUG Website

52. Join for the group Check upcoming events Get the slide decks from past events Share Documents Define User Goals

55. Summary Content First! User experience, not device experience Be future friendly, start using CSS3/HTML5 Use pre-processors to help manage code Conditionally load if possible (device channels).