The document discusses the benefits of using web components for projects. Web components allow for reusable code snippets called custom elements that can be used across different sites and frameworks. They keep CSS and JavaScript encapsulated and make code maintenance easier. While older browsers don't support web components natively, polyfills allow them to work on most browsers. The author argues that within a few years the vast majority of traffic will be from modern browsers that support web components natively. They recommend starting to use web components now on new and existing projects to take advantage of their benefits.
15. My interface designer makes a
simple “button” for us to use
My team has to integrate my
designer’s “button” X number of
buttons X number of projects
16. My interface designer makes a
simple “button” for us to use
My team has to integrate my
designer’s “button” X number of
buttons X number of projects
...My “team” will screw this up
18. Shadow DOM keeps CSS scoped
Custom elements makes HTML semantic
Both make JS scoping simple
WC keeps design intentional
WC makes design sustainable
WC make web professionals happy!
19. Accessibility becomes manageable
Maintenance costs collapses
Cost of development collapses
Project churn is eliminated
All Future projects cost less
Each new project expands capabilities
WC make web managers happy!
20.
21.
22.
23.
24.
25. Escape the Drupal design island
● Reuse parts of your Drupal 7 sites in Drupal 8
● Enhance your Drupal 6,7,8 sites safely
● Can be used across CMSs
36. @btopro parsing the data
Last 90 days of 2019
● 84.6% -- Works natively
● 12.3% -- works with polyfills
● = 96.9% -- Will work with web components!
37. Global traffic stats - gs.statcounter.com
February 2019 (browserstack.com + physical devices)
● 🔥 Confirmed working -- 98.26%
● 🤗 Should work / unconfirmed -- 99.64%
● 🤗 Numbers are without progressive enhancement
● Let’s talk Edge / IE
38. We have to support IE / Edge!
gs.statcounter.com
45. HAXcms progressive enhancement strategy
btopro.com/all-screen-rights - All screens have rights
Numbers are MY personal strategy aligned with Government data
== NoJS / fallback version (11.1%)
== ES5 web components + Polyfill (4.3%)
🔥 Modern but old version - ES5 web components + Polyfill (4%, Firefox)
🔥 Evergreen / ES6 - ES6 web components (80.6% of traffic, today!)
49. My Guess 1 year from now
== NoJS / fallback version (10%)
🔥 Evergreen / ES6 - ES6 web components (90% of traffic)
50. My Guess 2 year from now
== NoJS / fallback version (5%)
🔥 Evergreen / ES6 - ES6 web components (95% of traffic)
51. So if your planning a project or starting one..
🔥 Talk about design and development needs across your portfolio
🔥 Look at what current projects could be augmented
🔥 Start small – We started with a single icon, then a button, then a menu
* Be mindful of progressive enhancement
🔥 There’s no reason to not use web components!
58. This site is built in HAXcms, all structure via a UI
59. Bryan Ollendyke
@btopro
College of Arts and Architecture
Office of Digital Learning
Michael Potter
@hey__mp
Eberly College of Science
Office of Digital Learning
Training after lunch
60. Additional opportunities
Tuesday
11:00am | Room 204 | Level 2
Creating a library agnostic approach to
sustainable Web Component development
Wednesday
4:00pm | Room 617 | Level 6
Make web development fun again, with web components!
Thursday
9:00am | BoF 1 | Exhibit Hall | Level 4
Web components BoF
Hinweis der Redaktion
Originally we would have made the link this way
Originally we would have made the link this way
The Custom Elements specification lays the foundation for designing and using new types of DOM elements.The shadow DOM specification defines how to use encapsulated style and markup in web components.The ES Modules specification defines the inclusion and reuse of JS documents in a standards based, modular, performant way.The HTML template element specification defines how to declare fragments of markup that go unused at page load, but can be instantiated later on at runtime.
The Custom Elements specification lays the foundation for designing and using new types of DOM elements.The shadow DOM specification defines how to use encapsulated style and markup in web components.The ES Modules specification defines the inclusion and reuse of JS documents in a standards based, modular, performant way.The HTML template element specification defines how to declare fragments of markup that go unused at page load, but can be instantiated later on at runtime.
The Custom Elements specification lays the foundation for designing and using new types of DOM elements.The shadow DOM specification defines how to use encapsulated style and markup in web components.The ES Modules specification defines the inclusion and reuse of JS documents in a standards based, modular, performant way.The HTML template element specification defines how to declare fragments of markup that go unused at page load, but can be instantiated later on at runtime.
The Custom Elements specification lays the foundation for designing and using new types of DOM elements.The shadow DOM specification defines how to use encapsulated style and markup in web components.The ES Modules specification defines the inclusion and reuse of JS documents in a standards based, modular, performant way.The HTML template element specification defines how to declare fragments of markup that go unused at page load, but can be instantiated later on at runtime.
Google w/ YouTube, Comcast w/ xfinity. Duration of the roll out involves planning and banking on when it’s time to jump