Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Looking Back to Move Forward: Building the Modern Web

19,771 views

Published on

My keynote presentation opening the NAGW National Conference in Albuquerque.

Published in: Internet, Software, Technology
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ https://www.ThesisScientist.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hey guys! Who wants to chat with me? More photos with me here 👉 http://www.bit.ly/katekoxx
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ https://www.ThesisScientist.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ www.ThesisScientist.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Looking Back to Move Forward: Building the Modern Web

  1. Building the modern web Rachel Andrew, NAGW 2015 Rachel Andrew, NAGW 2015
  2. Rachel Andrew, NAGW 2015
  3. Rachel Andrew, NAGW 2015
  4. Dancers do not need to use computers Rachel Andrew, NAGW 2015
  5. Rachel Andrew, NAGW 2015
  6. The web gave me a community Rachel Andrew, NAGW 2015
  7. Rachel Andrew, NAGW 2015
  8. “Knowing HTML” was a marketable skill Rachel Andrew, NAGW 2015
  9. Learning something one day - teaching it to someone else the next Rachel Andrew, NAGW 2015
  10. The web gave me a new career. Rachel Andrew, NAGW 2015
  11. The web was accessible, and had a culture of sharing knowledge. Rachel Andrew, NAGW 2015
  12. Font tags and nested tables Rachel Andrew, NAGW 2015
  13. <script type="text/javascript"> <!-- function MM_reloadPage(init) { if (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) { document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }} else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload(); } MM_reloadPage(true); //--> </script> Rachel Andrew, NAGW 2015
  14. The “Netscape Resize Fix” If the user resized their browser window positioned elements lost their positioning values. The “fix” was to reload the browser window on resize. Rachel Andrew, NAGW 2015
  15. Rachel Andrew, NAGW 2015
  16. Rachel Andrew, NAGW 2015
  17. Rachel Andrew, NAGW 2015
  18. Rachel Andrew, NAGW 2015
  19. … basic support of existing W3C standards has been sacrificed in the name of such innovation, needlessly fragmenting the Web and helping no one. — http://archive.webstandards.org/mission.html Rachel Andrew, NAGW 2015
  20. Our goal is to support these core standards and encourage browser makers to do the same, thereby ensuring simple, affordable access to Web technologies for all. — http://archive.webstandards.org/mission.html Rachel Andrew, NAGW 2015
  21. Rachel Andrew, NAGW 2015
  22. Encouraging designers to care about web standards Rachel Andrew, NAGW 2015
  23. The IE6 years Rachel Andrew, NAGW 2015
  24. Front-end developer 2005? Browser bugs expert Rachel Andrew, NAGW 2015
  25. Thanks to the hard work of countless WaSP members and supporters (like you), Tim Berners-Lee’s vision of the web as an open, accessible, and universal community is largely the reality. — http://www.webstandards.org/2013/03/01/our-work- here-is-done/ Rachel Andrew, NAGW 2015
  26. Browser vendors are implementing standard things in a standard way Rachel Andrew, NAGW 2015
  27. Innovation happens through the standards process Rachel Andrew, NAGW 2015
  28. Show stopping browser bugs when doing straightforward things in modern browsers are rare Rachel Andrew, NAGW 2015
  29. Is it all easy now? Rachel Andrew, NAGW 2015
  30. Studies show that a todo list is the most complex JavaScript app you can create before a newer, better framework is invented. — http://www.allenpike.com/2015/javascript- framework-fatigue/ Rachel Andrew, NAGW 2015
  31. We’re creating complexity Hiding the simple languages of the web behind tooling and process Rachel Andrew, NAGW 2015
  32. Rachel Andrew, NAGW 2015
  33. <div class="header"> <h1>My website</h1> <div class="nav"> </div> </div> <div class="article"></div> <div class="sidebar"></div> <div class="footer"></div> Rachel Andrew, NAGW 2015
  34. <header> <h1>My website</h1> <nav> </nav> </header> <article></article> <aside></aside> <footer></footer> Rachel Andrew, NAGW 2015
  35. Web Video Text Tracks Format (WebVTT) WEBVTT 1 00:00:22.230 --> 00:00:24.606 This is the first subtitle. 2 00:00:30.739 --> 00:00:34.074 This is the second. 3 00:00:34.159 --> 00:00:35.743 Third Rachel Andrew, NAGW 2015
  36. Rachel Andrew, NAGW 2015
  37. Rachel Andrew, NAGW 2015
  38. Time-dimensional pseudo-classes :current :past :future :current(p, li, dt, dd) { background: yellow; } :past(p, li, dt, dd) { background: transparent; color: #999999; } Rachel Andrew, NAGW 2015
  39. Rachel Andrew, NAGW 2015
  40. Rachel Andrew, NAGW 2015
  41. CSS Grid Layout <div class="wrapper"> <header class="header">Header</header> <aside class="sidebar">Sidebar</aside> <article class="content">Content</article> </div> Rachel Andrew, NAGW 2015
  42. .sidebar { grid-area: sidebar; } .content { grid-area: content; } .header { grid-area: header; } .wrapper { display: grid; grid-template-columns: 120px 10px 120px 10px 120px; grid-template-rows: auto; grid-template-areas: "header header header header header" "sidebar . content content content"; } Rachel Andrew, NAGW 2015
  43. Rachel Andrew, NAGW 2015
  44. Rachel Andrew, NAGW 2015
  45. “I’ll take a look if you create a Sass Mixin …” — via my inbox Rachel Andrew, NAGW 2015
  46. Emerging specifications like Grid remove the need for a lot of the preprocessing Rachel Andrew, NAGW 2015
  47. Rachel Andrew, NAGW 2015
  48. Rachel Andrew, NAGW 2015
  49. .ag1 { @include span(2 of 10); } .ag2 { @include span(6 of 10); @include clearfix; } .ag3 { @include span(2 of 10 last); } Rachel Andrew, NAGW 2015
  50. Rachel Andrew, NAGW 2015
  51. /* declare a grid and set up a 10 column grid with gutters */ .container { width: 90%; margin: 0 auto 0 auto; display: grid; grid-template-columns: [col] 4.25fr repeat(9, [gutter] 1fr [col] 4.25fr ) [gutter]; grid-template-rows: auto repeat(5, 100px); } /* boxes positioned like so */ /* heading in row 1 full width */ h1 { grid-column: col / span col 10; grid-row: 1 / 2; } /* left hand sidebar */ .ag1 { grid-column: col / span gutter 2; grid-row: 2 / 3; } Rachel Andrew, NAGW 2015
  52. We should be all over a spec like grid. This is the future. Rachel Andrew, NAGW 2015
  53. Rachel Andrew, NAGW 2015
  54. By leaning on frameworks, are we masking the issues? Rachel Andrew, NAGW 2015
  55. Only by working with the specifications can we be part of improving them Rachel Andrew, NAGW 2015
  56. Sheer frustration drove much of the Web Standards movement Rachel Andrew, NAGW 2015
  57. My fear is that our reliance on frameworks will stop us pushing for better solutions Rachel Andrew, NAGW 2015
  58. Rachel Andrew, NAGW 2015
  59. There are always compromises. They shouldn’t be the same for every project. Rachel Andrew, NAGW 2015
  60. Standardising on tools should not be at the expense of learning HTML, CSS and JavaScript Rachel Andrew, NAGW 2015
  61. Use your tools and frameworks lightly Rachel Andrew, NAGW 2015
  62. Be ready to put them aside when they don’t suit a project Rachel Andrew, NAGW 2015
  63. Don’t become an expert in one brand of hammer. Become a master carpenter. Rachel Andrew, NAGW 2015
  64. Develop timeless skills Rachel Andrew, NAGW 2015
  65. It is HTML, CSS, JavaScript How you get there is just process. Rachel Andrew, NAGW 2015
  66. The “space junk” of the web Rachel Andrew, NAGW 2015
  67. Will we be still using frameworks to abstract away layout hacks, long after there is any need for the hacks? Rachel Andrew, NAGW 2015
  68. Best practices can become anti-patterns HTTP/2 will see many of our best practices become bad practices. — Image Sprites — Domain Sharding — Concatenating CSS and JavaScript Rachel Andrew, NAGW 2015
  69. Whose time are we saving? Rachel Andrew, NAGW 2015
  70. We write code once. It runs 100s of 1000s of times in the browsers of our visitors. Rachel Andrew, NAGW 2015
  71. “When I look around, I see our community spending a lot of time coming up with new tools and techniques to make our jobs easier. To ship faster. And it’s not that I’m against efficiency, but I think we need to consider the implications of our decisions. And if one of those implications is making our users suffer—or potentially suffer—in order to make our lives easier, I think we need to consider their needs above our own.” — http://aaron-gustafson.com/notebook/who-should- pay/ Rachel Andrew, NAGW 2015
  72. Rachel Andrew, NAGW 2015
  73. The myth of temporary Rachel Andrew, NAGW 2015
  74. The web is inherently accessible. We choose to protect that, or to break it. Rachel Andrew, NAGW 2015
  75. Rachel Andrew, NAGW 2015
  76. I believe progressive enhancement is still the best approach we have Rachel Andrew, NAGW 2015
  77. “a robust site or application in the more traditional sense minimises its dependencies. The minimum dependency for a web site should be an internet connection and the ability to parse HTML.” — http://www.bbc.co.uk/guidelines/futuremedia/ accessibility/html/progressive-enhancement.shtml Rachel Andrew, NAGW 2015
  78. Start with the core experience Rachel Andrew, NAGW 2015
  79. What is the minimum that I need to ship? How can I ensure as I iterate I protect the core experience for everyone? Rachel Andrew, NAGW 2015
  80. We Ship. We Iterate. Rachel Andrew, NAGW 2015
  81. How should we integrate third party code? Rachel Andrew, NAGW 2015
  82. Not Invented Here Rachel Andrew, NAGW 2015
  83. “Are you afraid to write code? Does the thought linger in your brain that somewhere out there somebody has already done this? Do you find yourself trapped in an analysis cycle where nothing is getting done? Is your product mutating to accommodate third party components? If yes, then perhaps you are suffering from invented-here syndrome.” — http://mortoray.com/2015/02/25/invented-here-syndrome/ Rachel Andrew, NAGW 2015
  84. Avoid turning shortcuts and third party code into dependencies Rachel Andrew, NAGW 2015
  85. Dependency Inversion Rachel Andrew, NAGW 2015
  86. “High level modules should not depend upon low- level modules. Both should depend upon abstractions. Abstractions should never depend upon details. Details should depend upon abstractions.” — http://www.objectmentor.com/resources/articles/ dip.pdf Rachel Andrew, NAGW 2015
  87. Rachel Andrew, NAGW 2015
  88. Progressively enhanced UI — JavaScript implementation based on the regular HTML5 Video element — Static maps that become draggable and zoomable - avoiding creating a dependency on one maps provider or library — Ordering items via a form input - that become drag and drop if the user has JavaScript Rachel Andrew, NAGW 2015
  89. You can’t do everything You can do something Rachel Andrew, NAGW 2015
  90. “A 100% pure progressively-enhanced website may not be practical on every single project you will ever encounter. While that sort of purity can exist, it’s unlikely in many business scenarios. Budgets, timelines: these things exist. Progressive enhancement isn’t a zero sum game; it’s a continuum, just like the Web.” — http://sixtwothree.org/posts/the-practical-case-for-progressive- enhancement Rachel Andrew, NAGW 2015
  91. If your site doesn’t load who misses out? What do they lose? Rachel Andrew, NAGW 2015
  92. Giving back Rachel Andrew, NAGW 2015
  93. Where does our next generation of web professionals come from? Rachel Andrew, NAGW 2015
  94. If you have been doing this for a year, there is someone 6 months in who you are ideally placed to help. Rachel Andrew, NAGW 2015
  95. You will learn by teaching Rachel Andrew, NAGW 2015
  96. Contribute to the standards that make up the web Rachel Andrew, NAGW 2015
  97. What do authors think? Rachel Andrew, NAGW 2015
  98. Learn how the modern standards process works Rachel Andrew, NAGW 2015
  99. Rachel Andrew, NAGW 2015
  100. If authors do not offer feedback, the final specification will reflect our needs as understood by people who do not build websites. Rachel Andrew, NAGW 2015
  101. To make an impact on a specification you need to do so while it is still a draft There is no point complaining about something that is finished. You have your chance to make your case during the open standards process. Rachel Andrew, NAGW 2015
  102. Grid Layout and “gutters” Rachel Andrew, NAGW 2015
  103. .wrapper { display: grid; grid-template-columns: 120px 10px 120px 10px 120px; grid-template-rows: auto; grid-template-areas: "header header header header header" "sidebar . content content content"; } Rachel Andrew, NAGW 2015
  104. .wrapper { display: grid; grid-template-columns: repeat(11, [col] 4fr [gutter] 3.5fr ) [col] 4fr [gutter]; grid-template-rows: auto repeat(4, [row] auto [gutter] 15px); } Rachel Andrew, NAGW 2015
  105. I believed the grid needed column and row gaps much like multi-column layout has the column-gap property Rachel Andrew, NAGW 2015
  106. .wrapper { display: grid; grid-template-columns: repeat(11, [col] 4fr [gutter] 3.5fr ) [col] 4fr [gutter]; grid-template-rows: auto repeat(4, [row] auto [gutter] 15px); } Rachel Andrew, NAGW 2015
  107. .wrapper { display: grid; grid-column-gap: 1em; grid-row-gap: 1em; grid-template-columns: repeat(12, [col] 4fr ); grid-template-rows: auto; } Rachel Andrew, NAGW 2015
  108. Solving the gutter problem — https://rachelandrew.co.uk/archives/2015/06/19/css- grid-layout-solving-the-gutter-problem/ — Post to the CSS WG list about the issue Rachel Andrew, NAGW 2015
  109. Put together use cases. Show issues clearly. Rachel Andrew, NAGW 2015
  110. Look for the issues already listed in draft specifications Rachel Andrew, NAGW 2015
  111. I am hopeful that contributing to standards is going to get easier Rachel Andrew, NAGW 2015
  112. The CSS Working Group may move to GitHub for issues in 2016 Rachel Andrew, NAGW 2015
  113. The Web Incubator Community Group — https://www.w3.org/community/wicg/ Rachel Andrew, NAGW 2015
  114. “Their goal is to take the lessons learned during the RICG’s responsive images slog and adapt web standards to match.” — https://www.w3.org/community/respimg/2015/07/09/ wicg/ Rachel Andrew, NAGW 2015
  115. The Specification Forum http://discourse.wicg.io/ Rachel Andrew, NAGW 2015
  116. Keep an eye on CSS Houdini A task force working on drafts that seek to explain and expose different parts of CSS. This should ultimately make it easier to polyfill, innovate, experiment and create entire new features. — https://wiki.css-houdini.org/ — https://dev.opera.com/articles/houdini/ Rachel Andrew, NAGW 2015
  117. Browsers vendors and the CSS WG alike are looking for “signals” from authors — are people talking about this spec? — are they writing about it, speaking at conferences? — are they directly requesting the features? Rachel Andrew, NAGW 2015
  118. Rachel Andrew, NAGW 2015
  119. Make a noise so that browser vendors hear what we want implemented Rachel Andrew, NAGW 2015
  120. Adopt an emerging specification! Rachel Andrew, NAGW 2015
  121. Some final thoughts Rachel Andrew, NAGW 2015
  122. Things are changing fast. Solid understanding of core web technologies has proved timeless. Rachel Andrew, NAGW 2015
  123. Ensuring maximum accessibility should be at the heart of all you do. Rachel Andrew, NAGW 2015
  124. Find ways to contribute Your voice & the voice of the people you build sites for is important. Rachel Andrew, NAGW 2015
  125. Thank you. @rachelandrew https://rachelandrew.co.uk/presentations/nagw Rachel Andrew, NAGW 2015

×