├── .eslintignore ├── .eslintrc.js ├── .gitignore ├── .travis.yml ├── README.md ├── app.js ├── app.yaml ├── assets └── images │ ├── a-future-called-web-components-at-front-trends.jpg │ ├── a-quick-polymer-intro.png │ ├── accessibility-is-my-favorite-part-of-the-platform-at-google-io-2016.jpg │ ├── accessibility-of-web-components-at-jsconf-us-cover.jpg │ ├── accessibility-of-web-components-at-jsconf-us.jpg │ ├── an-introduction-to-web-components-at-web-components-london-cover.jpg │ ├── an-introduction-to-web-components-at-web-components-london.jpg │ ├── as-i-walk-through-the-valley-of-the-shadow-of-dom-at-jqcon.jpg │ ├── building-a-custom-tag-input-with-skate-js.png │ ├── building-mobile-web-applications-with-brick-at-full-frontal-cover.jpg │ ├── building-mobile-web-applications-with-brick-at-full-frontal.jpg │ ├── building-the-google-io-web-app-launching-a-progressive-web-app-on-Google-com-at-google-io-2016.jpg │ ├── complementarity-of-react-and-web-components-at-reactjs-conf.jpg │ ├── componentize-the-web-back-to-the-browser-at-lxjs.jpg │ ├── componentize-your-app-with-polymer-elements.jpg │ ├── components-and-modules-at-edgeconf.jpg │ ├── creating-container-components-in-web-components-and-angular.jpg │ ├── custom-elements-interop-angular.png │ ├── customelements-inherit.png │ ├── customelements-relativetime.png │ ├── customelements-time.png │ ├── devbytes-customelements.png │ ├── devbytes-htmlimports.png │ ├── devbytes-shadowdom.png │ ├── devbytes-template.png │ ├── dominating-shadow-dom-cover.jpg │ ├── dominating-shadow-dom.jpg │ ├── dont-stop-thinking-about-tomorrow-slides.png │ ├── dont-stop-thinking-about-tomorrow.png │ ├── easy-composition-and-reuse-with-web-components-at-chrome-devsummit.jpg │ ├── end-of-first-quarter-2015.jpg │ ├── end-of-second-quarter-2015.jpg │ ├── future-css-in-web-components-at-css-conf.jpg │ ├── gifs-vs-web-components-at-jsconf-eu.png │ ├── github-custom-element.jpg │ ├── high-performance-web-components.jpg │ ├── how-should-i-name-my-element.jpg │ ├── htmlimports-dependency.png │ ├── interview-with-daniel-buchner.jpg │ ├── interview-with-joshua-peek.jpg │ ├── interview-with-michael-bleigh.jpg │ ├── interview-with-rob-dodson.jpg │ ├── interview-with-travis-leithead.jpg │ ├── introducing-server-components.jpg │ ├── introducing-the-element-registry.png │ ├── introduction-to-web-components-and-polymer-at-dc-webcomponents.png │ ├── launch-inline-demo-small.gif │ ├── launch-main.gif │ ├── launch-preview-integration.png │ ├── launch-preview-small.gif │ ├── lets-build-some-apps-with-polymer-at-chrome-devsummit.jpg │ ├── making-polymer-elements-accessible-at-io.jpg │ ├── making-webgl-tools-with-polymer-at-html5devconf-cover.jpg │ ├── making-webgl-tools-with-polymer-at-html5devconf.jpg │ ├── multi-device-apps-with-web-components-at-jqcon.jpg │ ├── polymer-and-modern-web-apis-at-google-io.jpg │ ├── polymer-and-progressive-web-apps-building-on-the-modern-web-at-google-io-2016.jpg │ ├── polymer-and-the-web-components-revolution-at-io-cover.jpg │ ├── polymer-and-the-web-components-revolution-at-io.jpg │ ├── polymer-and-web-components-change-everything-you-know-about-web-development-at-io-cover.jpg │ ├── polymer-and-web-components-change-everything-you-know-about-web-development-at-io.jpg │ ├── polymer-at-chrome-dev-summit-cover.jpg │ ├── polymer-at-chrome-dev-summit.jpg │ ├── polymer-in-production.jpg │ ├── polymer-state-of-the-union-at-chrome-devsummit.jpg │ ├── polymer-summit.jpg │ ├── polymer-testing-tips.jpg │ ├── polymer-unit-testing.jpg │ ├── practical-lessons-from-a-year-of-building-web-components-at-google-io-2016.jpg │ ├── progressive-performant-polymer-pick-three-at-google-io-2016.jpg │ ├── quick-trick-using-template-to-delay-loading-of-images.jpg │ ├── real-time-apps-with-polymer-and-firebase.png │ ├── return-of-inspector-web-at-fronteers-cover.jpg │ ├── return-of-inspector-web-at-fronteers.jpg │ ├── serverless-applications-powered-by-web-components.jpg │ ├── shadowdom-architecture.png │ ├── shadowdom-content.png │ ├── shadowdom-devtools.png │ ├── shadowdom-settings.png │ ├── shadowdom-video.png │ ├── styling-web-components-using-a-shared-style-sheet.png │ ├── the-cure-for-your-web-components-hangover-at-jquery-uk.jpg │ ├── the-road-to-web-components-at-empirejs.jpg │ ├── the-web-platform-cutting-edge-at-google-io.jpg │ ├── there-is-an-element-for-that.jpg │ ├── turn-your-phone-into-a-motion-controller-with-polymer.jpg │ ├── unlock-the-next-era-of-ui-development-with-polymer-at-io-cover.jpg │ ├── unlock-the-next-era-of-ui-development-with-polymer-at-io.jpg │ ├── web-component-challenges.png │ ├── web-component-mashups-at-3am-at-sfhtml5-cover.jpg │ ├── web-component-mashups-at-3am-at-sfhtml5.jpg │ ├── web-components-a-chance-to-create-the-future-at-sfhtml5.jpg │ ├── web-components-a-new-way-of-building-web-apps-at-bdconf-cover.jpg │ ├── web-components-a-new-way-of-building-web-apps-at-bdconf.jpg │ ├── web-components-a-tectonic-shift-for-web-development-at-google-io-cover.jpg │ ├── web-components-a-tectonic-shift-for-web-development-at-google-io.jpg │ ├── web-components-and-the-future-of-css-cover.png │ ├── web-components-and-the-future-of-css.png │ ├── web-components-and-the-future-of-web-development-at-meta-refresh-cover.jpg │ ├── web-components-and-the-future-of-web-development-at-meta-refresh.jpg │ ├── web-components-best-practices.jpg │ ├── web-components-can-do-that-at-fitc-cover.jpg │ ├── web-components-can-do-that-at-fitc.jpg │ ├── web-components-from-jquery-polymer.png │ ├── web-components-getting-started-at-state-of-the-browser.jpg │ ├── web-components-in-firefox-os-cover.png │ ├── web-components-in-firefox-os.png │ ├── web-components-london-soledad-penades.png │ ├── web-components-revolution-at-cascade-cover.jpg │ ├── web-components-revolution-at-cascade.jpg │ ├── web-components-the-future-is-here-cover.jpg │ ├── web-components-the-future-is-here.jpg │ ├── web-components-why-you-are-already-an-expert-at-web-directions-cover.jpg │ ├── web-components-why-you-are-already-an-expert-at-web-directions.jpg │ ├── webcomponents-plus-backbone-a-game-changing-combination-at-backbone-conf.jpg │ ├── what-are-custom-elements-cover.jpg │ ├── what-are-custom-elements.jpg │ ├── why-web-components-are-so-important.png │ ├── why-web-components.jpg │ ├── why-you-should-be-using-web-components-and-how-at-devweek.jpg │ ├── x-tag-the-web-components-shuga-lib-at-sfhtml5-cover.jpg │ ├── x-tag-the-web-components-shuga-lib-at-sfhtml5.jpg │ └── yo-polymer-at-dotjs.jpg ├── authors.js ├── client-secret.json.enc ├── documents ├── articles │ ├── a-bet-on-web-components-and-embercomponent-synchronicity.html.md │ ├── a-detailed-introduction-to-custom-elements.html.md │ ├── a-guide-to-web-components.html.md │ ├── a-quick-polymer-introduction.html.md │ ├── a-w3c-custom-elements-alternative.html.md │ ├── accessibility-and-the-shadow-dom.html.md │ ├── accessible-web-components.html.md │ ├── best-practice-creating-custom-elements.html.md │ ├── bringing-componentization-to-the-web-an-overview-of-web-components.html.md │ ├── bringing-custom-elements-to-ie8.html.md │ ├── build-a-real-time-polymer-to-do-app.html.md │ ├── building-a-custom-tag-input-with-skate-js.html.md │ ├── component-interop-with-react-and-custom-elements.html.md │ ├── creating-polymer-chat-app-material-design.html.md │ ├── creating-semantic-sites-with-web-components-and-jsonld.html.md │ ├── custom-elements-defining-new-elements-in-html.html.md │ ├── custom-elements-interop-angular.html.md │ ├── custom-elements-v1.html.md │ ├── discoverability-for-web-components.html.md │ ├── end-of-first-quarter-2015.html.md │ ├── end-of-second-quarter-2015.html.md │ ├── exploring-html-imports.html.md │ ├── extending-styles.html.md │ ├── extensible-web-components.html.md │ ├── guitar-tuner.html.md │ ├── hands-on-with-polymer-1.html.md │ ├── how-should-i-name-my-element.html.md │ ├── html-imports-include-for-the-web.html.md │ ├── html-new-template-tag-standardizing-client-side-templating.html.md │ ├── html-partials-includes-webcomponents-way.md │ ├── inheritance-and-composition-with-polymer.html.md │ ├── integrating-web-components-with-angularjs.html.md │ ├── interview-with-daniel-buchner.html.md │ ├── interview-with-joshua-peek.html.md │ ├── interview-with-michael-bleigh.html.md │ ├── interview-with-rob-dodson.html.md │ ├── interview-with-travis-leithead.html.md │ ├── introducing-server-components.md │ ├── introducing-the-new-element-registry.html.md │ ├── introduction-to-custom-elements.html.md │ ├── introduction-to-html-imports.html.md │ ├── introduction-to-shadow-dom.html.md │ ├── introduction-to-template-element.html.md │ ├── ios-application-with-polymer-1-0.html.md │ ├── microsoft-edge-and-web-components.html.md │ ├── mozilla-and-web-components-update.html.md │ ├── my-experience-with-the-polymer-app-route.html.md │ ├── on-the-origin-of-species-web-components-from-jquery-to-polymer.html.md │ ├── over-the-edge-web-components-are-an-endangered-species.html.md │ ├── platformjs-becomes-webcomponentsjs.html.md │ ├── please-welcome-polymer-1-7.html.md │ ├── polyfills-0-6-0.html.md │ ├── polymer-0-8-released.html.md │ ├── polymer-0-8-sneak-peek.html.md │ ├── polymer-1-0-released.html.md │ ├── polymer-2-preview.html.md │ ├── polymer-for-the-performance-obsessed.html.md │ ├── polymer-in-legacy-production.html.md │ ├── polymer-in-production.html.md │ ├── polymer-testing-tips.md │ ├── polymer-to-create-web-components.html.md │ ├── polymer-unit-testing.html.md │ ├── polymer-vs-x-tag-here-is-the-difference.html.md │ ├── polymer-web-components-with-marionettejs.html.md │ ├── practical-questions-around-web-components.html.md │ ├── principles-for-general-purpose-components.html.md │ ├── quick-trick-using-template-to-delay-loading-of-images.html.md │ ├── sane-usage-of-custom-elements.html.md │ ├── server-side-web-components-how-and-why.html.md │ ├── setting-up-your-production-ready-polymer-1-0-application-development.html.md │ ├── shadow-dom-101.html.md │ ├── shadow-dom-201-css-and-styling.html.md │ ├── shadow-dom-301-advanced-concepts-and-dom-apis.html.md │ ├── shadow-dom-custom-elements-update.html.md │ ├── shadow-dom-strategies-in-angular-2.html.md │ ├── shadow-dom-the-basics.html.md │ ├── sharing-styles-across-web-components-with-polymer-and-core-style.html.md │ ├── styling-web-components-using-a-shared-style-sheet.html.md │ ├── taming-polymer-with-systemjs-and-typescript-part-1.html.md │ ├── the-difference-between-polymer-and-angular.html.md │ ├── the-state-of-web-components.html.md │ ├── there-is-an-element-for-that.html.md │ ├── turn-your-phone-into-a-motion-controller-with-polymer.html.md │ ├── universal-web-components.html.md │ ├── upgrading-from-polymer-0-5-to-1-0.html.md │ ├── using-polymer-1-0-with-angular.html.md │ ├── web-component-challenges.md │ ├── web-components-accessibility-and-the-priority-of-constituencies.html.md │ ├── web-components-already-an-expert.html.md │ ├── web-components-and-progressive-enhancement.html.md │ ├── web-components-and-you-dangers-to-avoid.html.md │ ├── web-components-best-practices.html.md │ ├── web-components-in-production-use-are-we-there-yet.html.md │ ├── web-components-org-update.html.md │ ├── web-components-punch-list.html.md │ ├── web-components-with-mozillas-brick-and-x-tag.html.md │ ├── what-happened-to-web-components.html.md │ ├── what-is-shady-dom.html.md │ ├── what-kind-of-web-components-do-we-need.html.md │ ├── why-we-created-webcomponentsorg.html.md │ ├── why-web-components-are-so-important.md │ ├── why-web-components-will-make-the-web-a-better-place-for-our-users.html.md │ ├── why-web-components.html.md │ └── write-web-components-with-es2015.md ├── podcasts │ ├── 1-history-of-polymer.html.md │ ├── 110-the-amp-mobile-revolution.html.md │ ├── 111-extensible-web-components.html.md │ ├── 115-aia-polymer-and-web-components-with-angular-2.html.md │ ├── 121-the-webcomponentsorg-relaunch.html.md │ ├── 123-universal-web-components.html.md │ ├── 124-web-components-typescript-and-bears-oh-my.html.md │ ├── 126-gold-standard-checklist-for-web-components.html.md │ ├── 129-elix-project.html.md │ ├── 133-ionic-and-web-components.html.md │ ├── 136-polymer-summit-recap.html.md │ ├── 2-polymer-io.html.md │ ├── 21-building-component-based-systems-with-josh-crowther.html.md │ ├── 3-testing-polymer.html.md │ ├── 4-polymer-1-review.html.md │ ├── 42-web-components-with-rob-dodson-tushar-mathur-and-monica-dinculescu.html.md │ ├── 44-web-components-with-john-rogerson.html.md │ ├── 5-polymer-summit.html.md │ ├── 6-component-show.html.md │ ├── 65-strand-web-components.html.md │ ├── 66-custom-elements-and-skatejs.html.md │ ├── 7-chrome-dev-summit.html.md │ ├── 70-web-components-at-microsoft.html.md │ ├── 71-vaadin-elements.html.md │ ├── 79-basic-web-components-and-best-practices.html.md │ ├── 82-are-web-components-ready-now.html.md │ ├── 97-predix-ui-and-polymer.html.md │ ├── 98-server-side-web-components.html.md │ ├── 99-polymer-native.html.md │ ├── S04E02-polymer-and-webcomponents-vs-frameworks.md │ ├── are-web-components-ready-yet.html.md │ ├── customizing-the-web-with-rob-dodson-on-the-web-ahead.html.md │ ├── google-polymer-with-rob-dodson-and-eric-bidelman-on-javascript-jabber.html.md │ ├── hax-floss-weekly.md │ ├── marcy-sutton-on-shop-talk-show.html.md │ ├── mozilla-brick-uikit-for-the-web-on-the-web-platform-podcast.html.md │ ├── one-part-beer-three-parts-web-components.html.md │ ├── polymer-10.html.md │ ├── react-and-reactive-elements.html.md │ ├── rob-dodson-on-shop-talk-show.html.md │ ├── the-bosonic-project-on-the-web-platform-podcast.html.md │ ├── the-return-of-bosonic.html.md │ ├── the-web-components-community-on-the-web-platform-podcast.html.md │ ├── the-x-tag-project-on-the-web-platform-podcast.html.md │ ├── understanding-web-components-and-polymer.html.md │ ├── web-accessibility-for-javascript-components-and-custom-elements-on-the-web-platform-podcast.html.md │ ├── web-accessibility-in-polymer.html.md │ ├── web-components-and-wtf-is-shadow-dom.html.md │ ├── web-components-interop-and-polymer-on-the-web-platform-podcast.html.md │ ├── web-components-with-cory-house-on-dotnet-rocks.html.md │ ├── web-components-with-peter-gasston-on-the-web-ahead.html.md │ └── x-tag-the-x-generation-on-the-web-platform-podcast.html.md └── presentations │ ├── a-future-called-web-components-at-front-trends.html.md │ ├── a-future-called-web-components-at-html5-la.html │ ├── accessibility-is-my-favorite-part-of-the-platform-at-google-io-2016.html.md │ ├── accessibility-of-web-components-at-jsconf-us.html.md │ ├── an-introduction-to-web-components-at-web-components-london.html.md │ ├── as-i-walk-through-the-valley-of-the-shadow-of-dom-at-jqcon.html.md │ ├── building-mobile-web-applications-with-brick-at-full-frontal.html.md │ ├── building-the-google-io-web-app-launching-a-progressive-web-app-on-Google-com-at-google-io-2016.html.md │ ├── complementarity-of-react-and-web-components-at-reactjs-conf.html.md │ ├── componentize-the-web-back-to-the-browser-at-lxjs.html.md │ ├── componentize-your-app-with-polymer-elements.html.md │ ├── components-101-intro-to-fundamental-changes-in-html.html.md │ ├── components-201-designing-components-for-reuse.html.md │ ├── components-and-modules-panel-at-edgeconf.html.md │ ├── creating-container-components-in-web-components-and-angular.html.md │ ├── dominating-shadow-dom.html.md │ ├── dont-stop-thinking-about-tomorrow-angularjs-and-web-components.html.md │ ├── easy-composition-and-reuse-with-web-components-at-chrome-devsummit.html.md │ ├── future-css-in-web-components-at-css-conf.html.md │ ├── gifs-vs-web-components-at-jsconf-eu.html.md │ ├── high-performance-web-components.html.md │ ├── introduction-to-web-components-and-polymer-at-dc-webcomponents.html.md │ ├── lets-build-some-apps-with-polymer-at-chrome-devsummit.html.md │ ├── london-web-components-meetup-wilson-page-web-components-in-firefox-os.html.md │ ├── making-polymer-elements-accessible.html.md │ ├── making-webgl-tools-with-polymer-at-html5devconf.html.md │ ├── multi-device-apps-with-web-components-at-jqcon.html.md │ ├── polymer-and-modern-web-apis-at-google-io.html.md │ ├── polymer-and-progressive-web-apps-building-on-the-modern-web-at-google-io-2016.html.md │ ├── polymer-and-the-web-components-revolution-at-io.html.md │ ├── polymer-and-web-components-change-everything-you-know-about-web-development-at-io.html.md │ ├── polymer-at-chrome-dev-summit.html.md │ ├── polymer-state-of-the-union-at-chrome-devsummit.html.md │ ├── polymer-summit.html.md │ ├── practical-lessons-from-a-year-of-building-web-components-at-google-io-2016.html.md │ ├── progressive-performant-polymer-pick-three-at-google-io-2016.html.md │ ├── real-time-apps-with-polymer-and-firebase.html.md │ ├── return-of-inspector-web-at-fronteers.html.md │ ├── serverless-applications-powered-by-web-components.html.md │ ├── the-cure-for-your-web-components-hangover-at-jquery-uk.html.md │ ├── the-road-to-web-components-at-empirejs.html.md │ ├── the-web-platform-cutting-edge-at-google-io.html.md │ ├── unlock-the-next-era-of-ui-development-with-polymer-at-io.html.md │ ├── web-component-mashups-at-3am-at-sfhtml5.html.md │ ├── web-components-a-chance-to-create-the-future-at-sfhtml5.html.md │ ├── web-components-a-new-way-of-building-web-apps-at-bdconf.html.md │ ├── web-components-a-tectonic-shift-for-web-development-at-google-io.html.md │ ├── web-components-and-the-future-of-css.html.md │ ├── web-components-and-the-future-of-web-development-at-meta-refresh.html.md │ ├── web-components-can-do-that-at-fitc.html.md │ ├── web-components-getting-started-at-state-of-the-browser.html.md │ ├── web-components-revolution-at-cascade.html.md │ ├── web-components-the-future-is-here.html.md │ ├── web-components-why-you-are-already-an-expert-at-web-directions.html.md │ ├── webcomponents-plus-backbone-a-game-changing-combination-at-backbone-conf.html.md │ ├── what-are-custom-elements.html.md │ ├── why-you-should-be-using-web-components-and-how-at-devweek.html.md │ ├── x-tag-the-web-components-shuga-lib-at-sfhtml5.html.md │ └── yo-polymer-at-dotjs.html.md ├── gen.js ├── mock-gen.js ├── package.json ├── static ├── about.md ├── assets.md ├── introduction.md ├── launch-announcement.md ├── libraries.md ├── logo.svg ├── polyfills.md ├── resources.md └── specs.md └── test └── test.js /.eslintignore: -------------------------------------------------------------------------------- 1 | authors.js 2 | content-gen.js -------------------------------------------------------------------------------- /.eslintrc.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | "extends": "google", 3 | "parserOptions": { 4 | "ecmaVersion": 6, 5 | }, 6 | }; -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | content-gen.js 3 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: node_js 2 | node_js: 3 | - '6' 4 | cache: 5 | directories: 6 | - node_modules 7 | before_install: 8 | - 'if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then openssl aes-256-cbc -K $encrypted_5ae6bda58156_key -iv $encrypted_5ae6bda58156_iv 9 | -in client-secret.json.enc -out client-secret.json -d; fi' 10 | script: 11 | - node gen.js 12 | deploy: 13 | provider: gae 14 | skip_cleanup: true 15 | keyfile: client-secret.json 16 | project: web-components-resources 17 | default: true 18 | -------------------------------------------------------------------------------- /app.yaml: -------------------------------------------------------------------------------- 1 | runtime: nodejs8 2 | -------------------------------------------------------------------------------- /assets/images/a-future-called-web-components-at-front-trends.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/a-future-called-web-components-at-front-trends.jpg -------------------------------------------------------------------------------- /assets/images/a-quick-polymer-intro.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/a-quick-polymer-intro.png -------------------------------------------------------------------------------- /assets/images/accessibility-is-my-favorite-part-of-the-platform-at-google-io-2016.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/accessibility-is-my-favorite-part-of-the-platform-at-google-io-2016.jpg -------------------------------------------------------------------------------- /assets/images/accessibility-of-web-components-at-jsconf-us-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/accessibility-of-web-components-at-jsconf-us-cover.jpg -------------------------------------------------------------------------------- /assets/images/accessibility-of-web-components-at-jsconf-us.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/accessibility-of-web-components-at-jsconf-us.jpg -------------------------------------------------------------------------------- /assets/images/an-introduction-to-web-components-at-web-components-london-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/an-introduction-to-web-components-at-web-components-london-cover.jpg -------------------------------------------------------------------------------- /assets/images/an-introduction-to-web-components-at-web-components-london.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/an-introduction-to-web-components-at-web-components-london.jpg -------------------------------------------------------------------------------- /assets/images/as-i-walk-through-the-valley-of-the-shadow-of-dom-at-jqcon.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/as-i-walk-through-the-valley-of-the-shadow-of-dom-at-jqcon.jpg -------------------------------------------------------------------------------- /assets/images/building-a-custom-tag-input-with-skate-js.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/building-a-custom-tag-input-with-skate-js.png -------------------------------------------------------------------------------- /assets/images/building-mobile-web-applications-with-brick-at-full-frontal-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/building-mobile-web-applications-with-brick-at-full-frontal-cover.jpg -------------------------------------------------------------------------------- /assets/images/building-mobile-web-applications-with-brick-at-full-frontal.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/building-mobile-web-applications-with-brick-at-full-frontal.jpg -------------------------------------------------------------------------------- /assets/images/building-the-google-io-web-app-launching-a-progressive-web-app-on-Google-com-at-google-io-2016.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/building-the-google-io-web-app-launching-a-progressive-web-app-on-Google-com-at-google-io-2016.jpg -------------------------------------------------------------------------------- /assets/images/complementarity-of-react-and-web-components-at-reactjs-conf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/complementarity-of-react-and-web-components-at-reactjs-conf.jpg -------------------------------------------------------------------------------- /assets/images/componentize-the-web-back-to-the-browser-at-lxjs.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/componentize-the-web-back-to-the-browser-at-lxjs.jpg -------------------------------------------------------------------------------- /assets/images/componentize-your-app-with-polymer-elements.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/componentize-your-app-with-polymer-elements.jpg -------------------------------------------------------------------------------- /assets/images/components-and-modules-at-edgeconf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/components-and-modules-at-edgeconf.jpg -------------------------------------------------------------------------------- /assets/images/creating-container-components-in-web-components-and-angular.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/creating-container-components-in-web-components-and-angular.jpg -------------------------------------------------------------------------------- /assets/images/custom-elements-interop-angular.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/custom-elements-interop-angular.png -------------------------------------------------------------------------------- /assets/images/customelements-inherit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/customelements-inherit.png -------------------------------------------------------------------------------- /assets/images/customelements-relativetime.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/customelements-relativetime.png -------------------------------------------------------------------------------- /assets/images/customelements-time.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/customelements-time.png -------------------------------------------------------------------------------- /assets/images/devbytes-customelements.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/devbytes-customelements.png -------------------------------------------------------------------------------- /assets/images/devbytes-htmlimports.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/devbytes-htmlimports.png -------------------------------------------------------------------------------- /assets/images/devbytes-shadowdom.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/devbytes-shadowdom.png -------------------------------------------------------------------------------- /assets/images/devbytes-template.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/devbytes-template.png -------------------------------------------------------------------------------- /assets/images/dominating-shadow-dom-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/dominating-shadow-dom-cover.jpg -------------------------------------------------------------------------------- /assets/images/dominating-shadow-dom.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/dominating-shadow-dom.jpg -------------------------------------------------------------------------------- /assets/images/dont-stop-thinking-about-tomorrow-slides.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/dont-stop-thinking-about-tomorrow-slides.png -------------------------------------------------------------------------------- /assets/images/dont-stop-thinking-about-tomorrow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/dont-stop-thinking-about-tomorrow.png -------------------------------------------------------------------------------- /assets/images/easy-composition-and-reuse-with-web-components-at-chrome-devsummit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/easy-composition-and-reuse-with-web-components-at-chrome-devsummit.jpg -------------------------------------------------------------------------------- /assets/images/end-of-first-quarter-2015.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/end-of-first-quarter-2015.jpg -------------------------------------------------------------------------------- /assets/images/end-of-second-quarter-2015.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/end-of-second-quarter-2015.jpg -------------------------------------------------------------------------------- /assets/images/future-css-in-web-components-at-css-conf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/future-css-in-web-components-at-css-conf.jpg -------------------------------------------------------------------------------- /assets/images/gifs-vs-web-components-at-jsconf-eu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/gifs-vs-web-components-at-jsconf-eu.png -------------------------------------------------------------------------------- /assets/images/github-custom-element.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/github-custom-element.jpg -------------------------------------------------------------------------------- /assets/images/high-performance-web-components.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/high-performance-web-components.jpg -------------------------------------------------------------------------------- /assets/images/how-should-i-name-my-element.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/how-should-i-name-my-element.jpg -------------------------------------------------------------------------------- /assets/images/htmlimports-dependency.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/htmlimports-dependency.png -------------------------------------------------------------------------------- /assets/images/interview-with-daniel-buchner.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/interview-with-daniel-buchner.jpg -------------------------------------------------------------------------------- /assets/images/interview-with-joshua-peek.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/interview-with-joshua-peek.jpg -------------------------------------------------------------------------------- /assets/images/interview-with-michael-bleigh.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/interview-with-michael-bleigh.jpg -------------------------------------------------------------------------------- /assets/images/interview-with-rob-dodson.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/interview-with-rob-dodson.jpg -------------------------------------------------------------------------------- /assets/images/interview-with-travis-leithead.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/interview-with-travis-leithead.jpg -------------------------------------------------------------------------------- /assets/images/introducing-server-components.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/introducing-server-components.jpg -------------------------------------------------------------------------------- /assets/images/introducing-the-element-registry.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/introducing-the-element-registry.png -------------------------------------------------------------------------------- /assets/images/introduction-to-web-components-and-polymer-at-dc-webcomponents.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/introduction-to-web-components-and-polymer-at-dc-webcomponents.png -------------------------------------------------------------------------------- /assets/images/launch-inline-demo-small.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/launch-inline-demo-small.gif -------------------------------------------------------------------------------- /assets/images/launch-main.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/launch-main.gif -------------------------------------------------------------------------------- /assets/images/launch-preview-integration.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/launch-preview-integration.png -------------------------------------------------------------------------------- /assets/images/launch-preview-small.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/launch-preview-small.gif -------------------------------------------------------------------------------- /assets/images/lets-build-some-apps-with-polymer-at-chrome-devsummit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/lets-build-some-apps-with-polymer-at-chrome-devsummit.jpg -------------------------------------------------------------------------------- /assets/images/making-polymer-elements-accessible-at-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/making-polymer-elements-accessible-at-io.jpg -------------------------------------------------------------------------------- /assets/images/making-webgl-tools-with-polymer-at-html5devconf-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/making-webgl-tools-with-polymer-at-html5devconf-cover.jpg -------------------------------------------------------------------------------- /assets/images/making-webgl-tools-with-polymer-at-html5devconf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/making-webgl-tools-with-polymer-at-html5devconf.jpg -------------------------------------------------------------------------------- /assets/images/multi-device-apps-with-web-components-at-jqcon.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/multi-device-apps-with-web-components-at-jqcon.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-modern-web-apis-at-google-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-modern-web-apis-at-google-io.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-progressive-web-apps-building-on-the-modern-web-at-google-io-2016.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-progressive-web-apps-building-on-the-modern-web-at-google-io-2016.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-the-web-components-revolution-at-io-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-the-web-components-revolution-at-io-cover.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-the-web-components-revolution-at-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-the-web-components-revolution-at-io.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-web-components-change-everything-you-know-about-web-development-at-io-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-web-components-change-everything-you-know-about-web-development-at-io-cover.jpg -------------------------------------------------------------------------------- /assets/images/polymer-and-web-components-change-everything-you-know-about-web-development-at-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-and-web-components-change-everything-you-know-about-web-development-at-io.jpg -------------------------------------------------------------------------------- /assets/images/polymer-at-chrome-dev-summit-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-at-chrome-dev-summit-cover.jpg -------------------------------------------------------------------------------- /assets/images/polymer-at-chrome-dev-summit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-at-chrome-dev-summit.jpg -------------------------------------------------------------------------------- /assets/images/polymer-in-production.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-in-production.jpg -------------------------------------------------------------------------------- /assets/images/polymer-state-of-the-union-at-chrome-devsummit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-state-of-the-union-at-chrome-devsummit.jpg -------------------------------------------------------------------------------- /assets/images/polymer-summit.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-summit.jpg -------------------------------------------------------------------------------- /assets/images/polymer-testing-tips.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-testing-tips.jpg -------------------------------------------------------------------------------- /assets/images/polymer-unit-testing.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/polymer-unit-testing.jpg -------------------------------------------------------------------------------- /assets/images/practical-lessons-from-a-year-of-building-web-components-at-google-io-2016.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/practical-lessons-from-a-year-of-building-web-components-at-google-io-2016.jpg -------------------------------------------------------------------------------- /assets/images/progressive-performant-polymer-pick-three-at-google-io-2016.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/progressive-performant-polymer-pick-three-at-google-io-2016.jpg -------------------------------------------------------------------------------- /assets/images/quick-trick-using-template-to-delay-loading-of-images.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/quick-trick-using-template-to-delay-loading-of-images.jpg -------------------------------------------------------------------------------- /assets/images/real-time-apps-with-polymer-and-firebase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/real-time-apps-with-polymer-and-firebase.png -------------------------------------------------------------------------------- /assets/images/return-of-inspector-web-at-fronteers-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/return-of-inspector-web-at-fronteers-cover.jpg -------------------------------------------------------------------------------- /assets/images/return-of-inspector-web-at-fronteers.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/return-of-inspector-web-at-fronteers.jpg -------------------------------------------------------------------------------- /assets/images/serverless-applications-powered-by-web-components.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/serverless-applications-powered-by-web-components.jpg -------------------------------------------------------------------------------- /assets/images/shadowdom-architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/shadowdom-architecture.png -------------------------------------------------------------------------------- /assets/images/shadowdom-content.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/shadowdom-content.png -------------------------------------------------------------------------------- /assets/images/shadowdom-devtools.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/shadowdom-devtools.png -------------------------------------------------------------------------------- /assets/images/shadowdom-settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/shadowdom-settings.png -------------------------------------------------------------------------------- /assets/images/shadowdom-video.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/shadowdom-video.png -------------------------------------------------------------------------------- /assets/images/styling-web-components-using-a-shared-style-sheet.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/styling-web-components-using-a-shared-style-sheet.png -------------------------------------------------------------------------------- /assets/images/the-cure-for-your-web-components-hangover-at-jquery-uk.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/the-cure-for-your-web-components-hangover-at-jquery-uk.jpg -------------------------------------------------------------------------------- /assets/images/the-road-to-web-components-at-empirejs.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/the-road-to-web-components-at-empirejs.jpg -------------------------------------------------------------------------------- /assets/images/the-web-platform-cutting-edge-at-google-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/the-web-platform-cutting-edge-at-google-io.jpg -------------------------------------------------------------------------------- /assets/images/there-is-an-element-for-that.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/there-is-an-element-for-that.jpg -------------------------------------------------------------------------------- /assets/images/turn-your-phone-into-a-motion-controller-with-polymer.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/turn-your-phone-into-a-motion-controller-with-polymer.jpg -------------------------------------------------------------------------------- /assets/images/unlock-the-next-era-of-ui-development-with-polymer-at-io-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/unlock-the-next-era-of-ui-development-with-polymer-at-io-cover.jpg -------------------------------------------------------------------------------- /assets/images/unlock-the-next-era-of-ui-development-with-polymer-at-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/unlock-the-next-era-of-ui-development-with-polymer-at-io.jpg -------------------------------------------------------------------------------- /assets/images/web-component-challenges.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-component-challenges.png -------------------------------------------------------------------------------- /assets/images/web-component-mashups-at-3am-at-sfhtml5-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-component-mashups-at-3am-at-sfhtml5-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-component-mashups-at-3am-at-sfhtml5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-component-mashups-at-3am-at-sfhtml5.jpg -------------------------------------------------------------------------------- /assets/images/web-components-a-chance-to-create-the-future-at-sfhtml5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-a-chance-to-create-the-future-at-sfhtml5.jpg -------------------------------------------------------------------------------- /assets/images/web-components-a-new-way-of-building-web-apps-at-bdconf-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-a-new-way-of-building-web-apps-at-bdconf-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-a-new-way-of-building-web-apps-at-bdconf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-a-new-way-of-building-web-apps-at-bdconf.jpg -------------------------------------------------------------------------------- /assets/images/web-components-a-tectonic-shift-for-web-development-at-google-io-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-a-tectonic-shift-for-web-development-at-google-io-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-a-tectonic-shift-for-web-development-at-google-io.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-a-tectonic-shift-for-web-development-at-google-io.jpg -------------------------------------------------------------------------------- /assets/images/web-components-and-the-future-of-css-cover.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-and-the-future-of-css-cover.png -------------------------------------------------------------------------------- /assets/images/web-components-and-the-future-of-css.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-and-the-future-of-css.png -------------------------------------------------------------------------------- /assets/images/web-components-and-the-future-of-web-development-at-meta-refresh-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-and-the-future-of-web-development-at-meta-refresh-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-and-the-future-of-web-development-at-meta-refresh.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-and-the-future-of-web-development-at-meta-refresh.jpg -------------------------------------------------------------------------------- /assets/images/web-components-best-practices.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-best-practices.jpg -------------------------------------------------------------------------------- /assets/images/web-components-can-do-that-at-fitc-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-can-do-that-at-fitc-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-can-do-that-at-fitc.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-can-do-that-at-fitc.jpg -------------------------------------------------------------------------------- /assets/images/web-components-from-jquery-polymer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-from-jquery-polymer.png -------------------------------------------------------------------------------- /assets/images/web-components-getting-started-at-state-of-the-browser.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-getting-started-at-state-of-the-browser.jpg -------------------------------------------------------------------------------- /assets/images/web-components-in-firefox-os-cover.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-in-firefox-os-cover.png -------------------------------------------------------------------------------- /assets/images/web-components-in-firefox-os.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-in-firefox-os.png -------------------------------------------------------------------------------- /assets/images/web-components-london-soledad-penades.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-london-soledad-penades.png -------------------------------------------------------------------------------- /assets/images/web-components-revolution-at-cascade-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-revolution-at-cascade-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-revolution-at-cascade.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-revolution-at-cascade.jpg -------------------------------------------------------------------------------- /assets/images/web-components-the-future-is-here-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-the-future-is-here-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-the-future-is-here.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-the-future-is-here.jpg -------------------------------------------------------------------------------- /assets/images/web-components-why-you-are-already-an-expert-at-web-directions-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-why-you-are-already-an-expert-at-web-directions-cover.jpg -------------------------------------------------------------------------------- /assets/images/web-components-why-you-are-already-an-expert-at-web-directions.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/web-components-why-you-are-already-an-expert-at-web-directions.jpg -------------------------------------------------------------------------------- /assets/images/webcomponents-plus-backbone-a-game-changing-combination-at-backbone-conf.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/webcomponents-plus-backbone-a-game-changing-combination-at-backbone-conf.jpg -------------------------------------------------------------------------------- /assets/images/what-are-custom-elements-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/what-are-custom-elements-cover.jpg -------------------------------------------------------------------------------- /assets/images/what-are-custom-elements.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/what-are-custom-elements.jpg -------------------------------------------------------------------------------- /assets/images/why-web-components-are-so-important.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/why-web-components-are-so-important.png -------------------------------------------------------------------------------- /assets/images/why-web-components.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/why-web-components.jpg -------------------------------------------------------------------------------- /assets/images/why-you-should-be-using-web-components-and-how-at-devweek.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/why-you-should-be-using-web-components-and-how-at-devweek.jpg -------------------------------------------------------------------------------- /assets/images/x-tag-the-web-components-shuga-lib-at-sfhtml5-cover.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/x-tag-the-web-components-shuga-lib-at-sfhtml5-cover.jpg -------------------------------------------------------------------------------- /assets/images/x-tag-the-web-components-shuga-lib-at-sfhtml5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/x-tag-the-web-components-shuga-lib-at-sfhtml5.jpg -------------------------------------------------------------------------------- /assets/images/yo-polymer-at-dotjs.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/assets/images/yo-polymer-at-dotjs.jpg -------------------------------------------------------------------------------- /client-secret.json.enc: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/webcomponents/community/e70b46d5b55e7785720cf25def87c9ee8c81c8b4/client-secret.json.enc -------------------------------------------------------------------------------- /documents/articles/a-bet-on-web-components-and-embercomponent-synchronicity.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: A Bet on Web Components and Ember.Component Synchronicity 3 | authors: [bill_heaton] 4 | date: 2015-03-04 5 | original_date: 2015-03-02 6 | link: http://pixelhandler.com/posts/a-bet-on-web-components-and-embercomponent-synchronicity 7 | category: articles 8 | layout: single 9 | tags: ['Ember', 'Custom Elements', 'HTML Imports', 'Shadow DOM', 'Template'] 10 | --- 11 | 12 | The Ember community is no stranger to componentization. The team for this JavaScript framework has been working hard on the implementation of Ember.Components as well as integrating these seemlessly with standard Web Components. 13 | 14 | The boundaries between Ember.Components and a Web Components are beginning to blur more and more. Making these two component models work together should be fairly easy. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/a-detailed-introduction-to-custom-elements.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: A Detailed Introduction To Custom Elements 3 | authors: [peter_gasston] 4 | date: 2014-03-12 5 | original_date: 2014-03-04 6 | link: http://coding.smashingmagazine.com/2014/03/04/introduction-to-custom-elements/ 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements'] 10 | --- 11 | 12 | You’ve probably heard all the noise about Web Components and how they’re going to change Web development forever. If you haven’t, you’ve either been living under a rock, are reading this article by accident, or have a full, busy life that doesn’t leave you time to read about unstable and speculative Web technologies. Well, not me. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/a-guide-to-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: A Guide to Web Components 3 | authors: [rob_dodson] 4 | date: 2014-01-19 5 | original_date: 2013-11-11 6 | link: http://css-tricks.com/modular-future-web-components/ 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements', 'Shadow DOM', 'Template'] 10 | --- 11 | 12 | Recently I was working with a client to train their internal teams on how to build web applications. During this process it occurred to me that the way we presently architect the front-end is very strange and even a bit broken. In many instances you’re either copying huge chunks of HTML out of some doc and then pasting that into your app (Bootstrap, Foundation, etc.), or you’re sprinkling the page with jQuery plugins which have to be configured using JavaScript. It puts us in the rather unfortunate position of having to choose between bloated HTML or mysterious HTML, and often we choose both. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/a-w3c-custom-elements-alternative.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: A W3C Custom Elements Alternative 3 | authors: [andrea_giammarchi] 4 | date: 2015-03-20 5 | original_date: 2014-07-15 6 | link: http://webreflection.blogspot.com.br/2014/07/a-w3c-custom-elements-alternative.html 7 | category: articles 8 | layout: single 9 | tags: ['Polyfills', 'Custom Elements'] 10 | --- 11 | 12 | ES6 introduced some goodness to JavaScript, and Weak or Set Maps are part of it. However, it is not entirely possible to polyfill these features without risking to be a bit obtrusive and not so backward compatible. When `webcomponents.js` initially went out, it was lacking support for older browsers and bringing in external arbitrary polyfills that were not playing so well together with few other libraries. On top of that, it was bringing features that if used on Android 2 phones or other cheap devices, where not performing so well and hence not that useful as part of the library. 13 | 14 | In order to avoid these little obstacles and brings at least Custom Elements out of the entire Web Components family in older Mobile browsers too, Andrea Giammarchi decided to invest some time and create a `document.registerElement` only polyfill with the goal of supporting as many mobile platforms as possible, and in a reasonable size over decent performance. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/accessibility-and-the-shadow-dom.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Accessibility and the Shadow DOM 3 | authors: [marcy_sutton] 4 | date: 2014-02-05 5 | original_date: 2014-02-05 6 | link: http://substantial.com/blog/2014/02/05/accessibility-and-the-shadow-dom/ 7 | category: articles 8 | layout: single 9 | tags: ['Accessibility', 'Shadow DOM'] 10 | --- 11 | 12 | Web Components, including Shadow DOM, are accessible because assistive technologies encounter pages as rendered, meaning the entire document is read as "one happy tree". With a polyfill to add broader support, users with modern browsers can interact with Web Components using a keyboard, touch or mouse. Screen readers will also read the page aloud, illustrating how Shadow DOM fits seamlessly into the regular DOM. 13 | 14 | It’s easy: to make Web Components accessible to all users, write accessible code. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/accessible-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Accessible Web Components - Part 1 3 | authors: [addy_osmani, alice_boxhall] 4 | date: 2014-05-14 5 | original_date: 2014-04-02 6 | link: http://www.polymer-project.org/articles/accessible-web-components.html 7 | category: articles 8 | layout: single 9 | tags: ['Accessibility', 'Custom Elements'] 10 | --- 11 | 12 | Custom Elements present a fantastic opportunity for us to improve accessibility on the web. 13 | 14 | To be accessible, elements need to work across multiple devices with varying screen-sizes and different kinds of input. Moreover, your elements should be usable by the broadest group of users, including those with disabilities. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/best-practice-creating-custom-elements.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Best Practice for Creating Custom Elements 3 | authors: [peter_gasston] 4 | date: 2015-02-16 5 | original_date: 2015-01-27 6 | link: http://www.broken-links.com/2015/01/27/best-practice-creating-custom-elements/ 7 | category: articles 8 | layout: single 9 | tags: ['Best Practices', 'Custom Elements'] 10 | --- 11 | 12 | It looks like custom elements, and web components in general, are beginning to break through into general developer consciousness, as I see more and more articles and talks discussing what they are, what they are good for, and how to make them. 13 | 14 | As they’re not yet being used heavily in development, however, I think there’s a good opportunity to define best practices in the way we use them. In this post I want to propose a best practice method for writing custom elements: I’ll do that by comparing two methods for creating custom elements, along with the advantages and drawbacks of each. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/bringing-componentization-to-the-web-an-overview-of-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bringing componentization to the web: An overview of Web Components 3 | authors: [travis_leithead, arron_eicholz] 4 | date: 2015-07-15 5 | original_date: 2015-07-14 6 | link: http://blogs.windows.com/msedgedev/2015/07/14/bringing-componentization-to-the-web-an-overview-of-web-components/ 7 | category: articles 8 | layout: single 9 | tags: ['Browser Support'] 10 | --- 11 | 12 | Four of our five most-requested platform features on UserVoice (Shadow DOM, Template, Custom Elements, HTML Imports) belong to the family of features called Web Components. In this post we’ll talk about Web Components and give our viewpoint, some background for those who may not be intimately familiar with them, and speculate a bit about where we might expect them to evolve in the future. To do it justice requires a bit of length, so sit back, grab a coffee (or non-caffeinated beverage) and read-on. In part two (coming tomorrow), we’ll address questions about our roadmap and plans for implementation. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/bringing-custom-elements-to-ie8.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bringing Custom Elements to IE8 3 | authors: [andrea_giammarchi] 4 | date: 2015-03-20 5 | original_date: 2015-03-20 6 | link: http://webreflection.blogspot.com.br/2015/03/bringing-custom-elements-to-ie8.html 7 | category: articles 8 | layout: single 9 | tags: ['Polyfills', 'Custom Elements'] 10 | --- 11 | 12 | Bringing modern Web standards to old browsers is always challenging, sometimes nearly impossible, but always beneficial for a graceful migrations approach. 13 | 14 | Before his latest talk in Helsinki, Andrea managed to accomplish something unexpected and relatively simple: he manged to make his Custom Element's `document.registerElement` [polyfill](https://github.com/WebReflection/document-register-element#document-register-element) compatible with Internet Explorer 8 too, together with the already wide list of old Mobile platforms supported since the very beginning. 15 | 16 | As result, when it's needed, and with a little extra effort, it is now possible to create components that won't break the old, even if not so good, Web platform. 17 | 18 | 19 | -------------------------------------------------------------------------------- /documents/articles/build-a-real-time-polymer-to-do-app.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Build A Real-Time Polymer To-Do App 3 | authors: [kevin_gleason] 4 | date: 2015-08-06 5 | original_date: 2015-08-06 6 | link: https://scotch.io/tutorials/build-a-real-time-polymer-to-do-app/ 7 | category: articles 8 | layout: single 9 | tags: ['polymer'] 10 | --- 11 | 12 | Building a realtime collaborative to-do application, where task status is synced in realtime across all connected devices as their state is changed can be a difficult thing to manage. Using Polymer an PubNub to build a collaborative application enables users to receive updates between connected devices, and to sync state. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/building-a-custom-tag-input-with-skate-js.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Building a custom tag input with Skate.js 3 | authors: [hector_zarco] 4 | date: 2017-1-4 5 | original_date: 2017-1-4 6 | image: building-a-custom-tag-input-with-skate-js.png 7 | link: https://hackernoon.com/building-a-custom-tag-input-with-skate-js-fbd4cdf744f#.ytkckk3gc 8 | category: articles 9 | --- 10 | 11 | Are you lost trying to build and use Web Components? Skate.js uses the platform and sheds some light on it. 12 | 13 | 14 | -------------------------------------------------------------------------------- /documents/articles/component-interop-with-react-and-custom-elements.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Component interop with React and Custom Elements 3 | authors: [addy_osmani] 4 | date: 2014-07-09 5 | original_date: 2014-07-08 6 | link: http://addyosmani.com/blog/component-interop-with-react-and-custom-elements/ 7 | category: articles 8 | layout: single 9 | tags: ['Interoperability', 'React', 'Polymer', 'Custom Elements'] 10 | --- 11 | 12 | Today we’ll look at how to wrap [React](http://facebook.github.io/react/) components using Custom Elements, allowing us to interop with Web Component- based libraries using the DOM as a simple configuration API. Similar to libraries like [Polymer](http://polymer-project.org/), React cares about composition, lifecycle events and modularity so seeing how well it fits with Web Components is an interesting thought experiment. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/creating-polymer-chat-app-material-design.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Creating a Polymer Chat App with Material Design 3 | authors: [tomomi_imura] 4 | date: 2015-02-14 5 | original_date: 2015-01-15 6 | link: http://www.pubnub.com/blog/creating-a-polymer-chat-app-with-material-design/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | We’ve published a wide variety of demos and tutorials showing you how to build a realtime chatroom with JavaScript; 10Chat with only 10 lines of JavaScript, AngularJS chat, going “native” with PhoneGap for Android and iOS, etc. 13 | 14 | I am showing how to create yet another chat app with Material Design using Polymer to create a simple but visually appealing app with a great user-experience. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/creating-semantic-sites-with-web-components-and-jsonld.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Creating semantic sites with Web Components and JSON-LD 3 | authors: [ewa_gasperowicz] 4 | date: 2015-04-26 5 | original_date: 2015-03-09 6 | link: http://updates.html5rocks.com/2015/03/creating-semantic-sites-with-web-components-and-jsonld 7 | category: articles 8 | layout: single 9 | tags: ['Semantics'] 10 | --- 11 | 12 | With the rising popularity of web components and supporting libraries like Polymer, custom elements become an attractive way to build UI features. The default encapsulation of custom elements makes them especially useful for creating independent widgets. 13 | 14 | While some of the widgets are self-contained, many of them rely on external data to present the content to the user - e.g., the current forecast for a weather widget or the address of a company for a map widget. 15 | 16 | It would be great if we could avoid repetition and ensure data consistency, by reusing the same data snippets to populate different widgets as well as inform search engines and other consumers about the content of our page. We can achieve this by using the [schema.org](http://schema.org/) standard and the [JSON-LD](http://www.w3.org/TR/json-ld/) format for our data. 17 | 18 | 19 | -------------------------------------------------------------------------------- /documents/articles/custom-elements-defining-new-elements-in-html.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Custom Elements: defining new elements in HTML 3 | authors: [eric_bidelman] 4 | date: 2014-01-19 5 | original_date: 2013-08-28 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/customelements/ 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements'] 10 | --- 11 | 12 | The web severely lacks expression. To see what I mean, take a peek at a "modern" web app like GMail. Modern web apps: built with `
` soup. There's nothing modern about `
` soup. And yet, this is how we build web apps. It's sad. Shouldn't we demand more from our platform? 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/custom-elements-interop-angular.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Custom Element Inter-op with Angular 2 3 | authors: [danny_blue] 4 | date: 2017-03-16 5 | original_date: 2016-06-30 6 | link: https://medium.com/@dee_bloo/custom-element-inter-op-with-angular-2-ed75f013a9ba 7 | category: articles 8 | image: custom-elements-interop-angular.png 9 | --- 10 | 11 | Learn how to use custom elements in Angular 2 12 | 13 | 14 | -------------------------------------------------------------------------------- /documents/articles/custom-elements-v1.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: "Custom elements v1: building reusable web components" 3 | authors: [eric_bidelman] 4 | date: 2016-08-01 5 | original_date: 2016-08-01 6 | link: https://developers.google.com/web/fundamentals/primers/customelements 7 | category: articles 8 | layout: single 9 | tags: ['Shadow DOM', 'Custom Elements'] 10 | --- 11 | 12 | With Custom Elements v1, web developers can create new HTML tags, beef-up existing HTML tags, or extend the components other developers have authored. The API is the foundation of web components. It brings a web standards-based way to create reusable components using nothing more than vanilla JS/HTML/CSS. The result is less code, modular code, and more reuse in our apps. 13 | -------------------------------------------------------------------------------- /documents/articles/discoverability-for-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Discoverability for Web Components 3 | authors: [zeno_rocha] 4 | date: 2015-05-27 5 | original_date: 2015-05-26 6 | link: https://medium.com/@zenorocha/discoverability-for-web-components-72ce29f128b2 7 | category: articles 8 | layout: single 9 | tags: ['Community'] 10 | --- 11 | 12 | In a world where you can create your own `` tag and distribute it with a simple ``, a whole range of options for composability and reusability emerges. 13 | 14 | Web Components are coming and there are many challenges coming along. How we connect component authors with component consumers is one of them. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/exploring-html-imports.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Exploring HTML Imports 3 | authors: [rob_dodson] 4 | date: 2014-01-19 5 | original_date: 2013-08-20 6 | link: http://robdodson.me/blog/2013/08/20/exploring-html-imports/ 7 | category: articles 8 | layout: single 9 | tags: ['HTML Imports'] 10 | --- 11 | 12 | Web Components have come a long way in the past few months and one of the technologies that I’m most interested in is HTML Imports (or “imports”, for short). Imports allow you to load additional documents into your page without having to write a bunch of Ajax. This is great for Custom Elements where you might want to import a suite of new tags. I spent the day playing with imports and thought it would be useful to write up my progress. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/extending-styles.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Extending Styles 3 | authors: [philip_walton] 4 | date: 2015-05-25 5 | original_date: 2015-05-20 6 | link: http://philipwalton.com/articles/extending-styles/ 7 | category: articles 8 | layout: single 9 | tags: ['Styling', 'Custom Elements', 'Shadow DOM'] 10 | --- 11 | 12 | The point of extending styles is to reuse code. If you’ve defined some base-level styles, you want to be able to use those styles again without having to rewrite them. And if you need to change those base-level styles, you want those changes to propagate throughout. 13 | 14 | Simply reusing code is easy. But reusing code in a way that is predictable, maintainable, and scalable is hard. Fortunately, computer scientists have been studying these problems for decades, and a lot of the principles of good software design apply to CSS as well 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/extensible-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Extensible Web Components 3 | authors: [jeremy_keith] 4 | date: 2016-08-03 5 | original_date: 2016-08-03 6 | link: https://adactio.com/journal/11052 7 | category: articles 8 | layout: single 9 | tags: ['Progressive Enhancement'] 10 | --- 11 | 12 | Using JavaScript with ShadowDOM, templates, and the other specs that together make up the web components ecosystem, you turn that inert span-like element into something all-singing and dancing. That’s great if the browser supports those technologies, and the JavaScript executes successfully. But if either of those conditions aren’t met, what you’re left with is basically a span. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/guitar-tuner.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Guitar Tuner 3 | authors: [paul_lewis] 4 | date: 2015-06-24 5 | original_date: 2015-06-17 6 | link: https://aerotwist.com/blog/guitar-tuner/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | Guitar Tuner, despite its cryptic name, is a web app that helps you tune a guitar. I’m sure you, like me, are shocked at this revelation. 13 | 14 | Web Components. It’s the perfect time to give Web Components a run out. In this case I had the idea that I could have three components: one to handle the audio input and analysis; one for the dial; and one for the instructions (tune up, down, etc). 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/hands-on-with-polymer-1.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Hands On With Polymer 1.0 3 | authors: [mike_schwartz] 4 | date: 2015-06-18 5 | original_date: 2015-06-18 6 | link: "http://moduscreate.com/hands-on-with-polymer-1-0/" 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | On May 29, 2015, the polymer team announced the release of Polymer 1.0. Since the release of Polymer 0.5 developer preview, the team has rewritten the library from the ground up, with increased performance and better functionality as results. 13 | 14 | Polymer is one of the first implementations of a user interface library built upon the Web Components standard. Web Components are not fully supported by browsers, but they provide a polyfill library, webcomponents.js, that provides enough functionality to support Web Components and Polymer. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/html-imports-include-for-the-web.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: 'HTML Imports: include for the web' 3 | authors: [eric_bidelman] 4 | date: 2014-01-19 5 | original_date: 2013-11-11 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/imports/ 7 | category: articles 8 | layout: single 9 | tags: ['HTML Imports'] 10 | --- 11 | 12 |

Think about how you load different types of resources on the web. For JS, we have <script src="">. For CSS, your go-to is probably <link rel="stylesheet"<. For images it's <img>>. Video has <video>. Audio, <audio>… Get to the point! The majority of the web's content has a simple and declarative way to load itself. Not so for HTML.

13 | -------------------------------------------------------------------------------- /documents/articles/html-new-template-tag-standardizing-client-side-templating.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: HTML's New Template Tag: standardizing client-side templating 3 | authors: [eric_bidelman] 4 | date: 2014-01-19 5 | original_date: 2013-02-26 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/template/ 7 | category: articles 8 | layout: single 9 | tags: ['Template'] 10 | --- 11 | 12 | The concept of templating is not new to web development. In fact, server-side templating languages/engines like Django (Python), ERB/Haml (Ruby), and Smarty (PHP) have been around for a long time. In the last couple of years however, we've seen an explosion of MVC frameworks spring up. All of them are slightly different, yet most share a common mechanic for rendering their presentational layer (aka da view): templates. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/html-partials-includes-webcomponents-way.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: HTML partials / includes WebComponents-way 3 | authors: [ tomalec ] 4 | date: 2016-09-18 5 | original_date: 2016-09-18 6 | link: 'http://starcounter.io/html-partialsincludes-webcomponents-way/' 7 | category: articles 8 | layout: single 9 | tags: ['HTML Imports', 'templates'] 10 | --- 11 | 12 |

Most of the bigger web project are designed to be modular. We all know that Custom Elements spec provides some modularity on individual HTML Element level, but is that all Web Components can give?

13 | -------------------------------------------------------------------------------- /documents/articles/inheritance-and-composition-with-polymer.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Inheritance and composition with Polymer 3 | authors: [pascal_precht] 4 | date: 2014-07-17 5 | original_date: 2014-07-17 6 | link: http://pascalprecht.github.io/2014/07/14/inheritance-and-composition-with-polymer/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | One of the biggest things that come with web components, is the fact that you can extend existing elements. And since your own custom elements are also just HTML elements, you can extend them as well as native elements. From a surface point of view there's no difference between native elements and custom elements. Let's take a look at how we can extend existing elements with Polymer. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/integrating-web-components-with-angularjs.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Integrating Web Components with AngularJS 3 | authors: [pascal_precht] 4 | date: 2014-10-26 5 | original_date: 2014-10-26 6 | link: http://pascalprecht.github.io/2014/10/25/integrating-web-components-with-angularjs/ 7 | category: articles 8 | layout: single 9 | tags: ['Interoperability', 'Angular'] 10 | --- 11 | 12 | This article focuses on the integration of Web Components with the AngularJS of today, what issues can occur, how to work around them and how the AngularJS of tomorrow will solve these issues in order to embrace the Web Components technologies. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/introducing-server-components.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Introducing Server Components 3 | authors: [tim_perry] 4 | date: 2016-07-20 5 | original_date: 2016-06-02 6 | image: introducing-server-components.jpg 7 | link: https://medium.com/@pimterry/introducing-server-components-84b4a296c664 8 | category: articles 9 | layout: single 10 | tags: ['Introduction', 'Server Components', 'Server Rendering'] 11 | --- 12 | 13 |

The developer experience of web components, with the power and simplicity of server-side development.

14 | 15 | -------------------------------------------------------------------------------- /documents/articles/introducing-the-new-element-registry.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Introducing the new element registry 3 | date: 2017-1-10 4 | original_date: 2017-1-10 5 | image: introducing-the-element-registry.png 6 | link: https://beta.webcomponents.org/launch-announcement 7 | category: articles 8 | --- 9 | 10 | With a growing web components community creating high quality components, we are excited to announce the new webcomponents.org including a new custom element registry. 11 | 12 | 13 | -------------------------------------------------------------------------------- /documents/articles/ios-application-with-polymer-1-0.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: iOS Application with Polymer 1.0 3 | authors: [ajit_kumar] 4 | date: 2015-07-03 5 | original_date: 2015-07-03 6 | link: http://blogs.walkingtree.in/2015/07/03/ios-application-with-polymer-1-0/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | In this article, we will go through the steps to create first Polymer 1.0 iOS application using Polymer Starter Kit. This shall help us create applications in Polymer and package them as iOS application, which can be installed and run on iOS devices, such as, iPhone, iPad, etc. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/microsoft-edge-and-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Microsoft Edge and Web Components 3 | authors: [travis_leithead, arron_eicholz] 4 | date: 2015-07-15 5 | original_date: 2015-07-15 6 | link: http://blogs.windows.com/msedgedev/2015/07/15/microsoft-edge-and-web-components/ 7 | category: articles 8 | layout: single 9 | tags: ['Browser Support'] 10 | --- 11 | 12 | Yesterday, we shared [our thoughts on the promise of Web Components](http://blogs.windows.com/msedgedev/2015/07/14/bringing-componentization-to-the-web-an-overview-of-web-components/). In this post, we’ll answer a couple of recurring questions we get about the technology, including our implementation roadmap and how we currently think about its priority in regards to other related platform work. We’re excited about the potential of these technologies, and today we’re excited to announce that we’re [beginning development on the HTML Template element](http://dev.modern.ie/platform/status/templateelement), one of the core Web Components technologies and the [#3 UserVoice request](https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6261273-template-element) from developers. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/mozilla-and-web-components-update.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Mozilla and Web Components: Update 3 | authors: [anne_van_kesteren] 4 | date: 2014-12-18 5 | original_date: 2014-12-15 6 | link: https://hacks.mozilla.org/2014/12/mozilla-and-web-components/ 7 | category: articles 8 | layout: single 9 | tags: ['Browser Support'] 10 | --- 11 | 12 | Mozilla has a long history of participating in standards development. The post below shows a real-time slice of how standards are debated and adopted. The goal is to update developers who are most affected by implementation decisions we make in Firefox. We are particularly interested in getting feedback from JavaScript library and framework developers. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/my-experience-with-the-polymer-app-route.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: My experience with the Polymer app-route 3 | authors: [tim_vanderlippe] 4 | date: 2016-05-22 5 | original_date: 2016-05-19 6 | link: https://timvdlippe.github.io/blog/#/b1-carbon-route 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'Custom Elements'] 10 | --- 11 | 12 | At the time of writing, the Polymer app-route is in beta. This element is designed to allow Polymer elements data-bind to the url of the site. This blog post will describe some of the issues encountered and depict solutions for said issues. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/over-the-edge-web-components-are-an-endangered-species.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Over the Edge: Web Components are an endangered species 3 | authors: [christian_heilmann] 4 | date: 2015-07-03 5 | original_date: 2015-07-01 6 | link: http://christianheilmann.com/2015/07/01/over-the-edge-web-components-are-an-endangered-species/ 7 | category: articles 8 | layout: single 9 | tags: ['Community'] 10 | --- 11 | 12 | Last week I ran the panel and the Web Components/Modules breakout session of the excellent Edge Conference in London, England and I think I did quite a terrible job. The reason was that the topic is too large and too fragmented and broken to be taken on as a bundle. 13 | 14 | Web Components are a great idea. Modules are a great idea. Together, they bring us hours and hours of fun debating where what should be done to create a well-performing, easy to maintain and all around extensible complex app for the web. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/platformjs-becomes-webcomponentsjs.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: platform.js ⇒ webcomponents.js 3 | authors: [polymer] 4 | date: 2014-10-20 5 | original_date: 2014-10-16 6 | link: https://blog.polymer-project.org/announcements/2014/10/16/platform-becomes-webcomponents/ 7 | category: articles 8 | layout: single 9 | tags: ['Polyfills'] 10 | --- 11 | 12 | We wanted to give developers an early heads up for a pretty big change coming down the line: the `platform.js` file that contains the Web Components polyfills will be renamed to `webcomponents.js` and transferred to [WebComponents.org](http://webcomponents.org/polyfills/). 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/please-welcome-polymer-1-7.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Please Welcome Polymer 1.7 3 | authors: [polymer] 4 | date: 2016-10-06 5 | original_date: 2016-10-03 6 | link: https://www.polymer-project.org/1.0/blog/2016-10-03-1.7-release.html 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'Custom Elements', 'Shadow DOM'] 10 | --- 11 | 12 | Polymer 1.7.0 provides forward compatibility features that let you build elements that run under both 1.0 and 2.0. 13 | 14 | -------------------------------------------------------------------------------- /documents/articles/polymer-0-8-released.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer 0.8 Released! 3 | authors: [taylor_savage] 4 | date: 2015-04-25 5 | original_date: 2015-03-27 6 | link: https://blog.polymer-project.org/updates/2015/03/27/why-0.8/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | While evolving the “Developer Preview” of Polymer, we made the tough decision to do a significant internal redesign. This move enabled us to move away from experimentation towards production-readiness, and is a big step towards a 1.0. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/polymer-0-8-sneak-peek.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer 0.8 Sneak Peek 3 | authors: [michael_bleigh] 4 | date: 2015-02-23 5 | original_date: 2015-02-23 6 | link: https://divshot.com/blog/web-components/polymer-0-8-sneak-peek/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | The next release of Polymer, 0.8, is going to be a doozy. It's the first release on the "heading towards production" track and it's going to have some pretty massive differences from previous versions. So what exactly is new, and what's changing? 13 | 14 | *Note: This data was gathered primarily from reading the [Polymer 0.8 Primer](https://github.com/Polymer/polymer/blob/0.8-preview/PRIMER.md) which is very, very extensive. I'm just hitting the highlights. Also note that any of this could change before the final release is cut.* 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/polymer-1-0-released.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer 1.0 Released 3 | authors: [taylor_savage] 4 | date: 2015-05-29 5 | original_date: 2015-05-29 6 | link: https://blog.polymer-project.org/announcements/2015/05/29/one-dot-oh/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | Today we’re incredibly excited to announce the 1.0 release of the Polymer library. 13 | 14 | Since the 0.5 “Developer Preview” release, we’ve re-written the library from the ground up, focusing on cross-browser performance while keeping the developer-friendly ergonomics. The new library is 3x faster on Chrome, 4x faster on Safari, and 36% less code than in developer preview. And it’s ready to be used in production applications. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/polymer-2-preview.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer 2.0 Preview 3 | authors: [polymer] 4 | date: 2016-09-09 5 | original_date: 2016-09-09 6 | link: https://www.polymer-project.org/1.0/blog/2016-09-09-polymer-2.0.html 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'Custom Elements', 'Shadow DOM'] 10 | --- 11 | 12 | The primary goal of the Polymer 2.0 release is to take advantage of native, cross-browser support for Web Components. 13 | 14 | Polymer 1.x is built on top of the so-called "v0" Web Components specs, which are supported natively only in Google Chrome; using Polymer in other browsers has always required the use of polyfills. 15 | 16 | -------------------------------------------------------------------------------- /documents/articles/polymer-for-the-performance-obsessed.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer for the Performance-obsessed 3 | authors: [paul_lewis] 4 | date: 2015-06-12 5 | original_date: 2015-06-11 6 | link: https://aerotwist.com/blog/polymer-for-the-performance-obsessed/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'Perfomance'] 10 | --- 11 | 12 | I'm building a small web app at the moment, and so I've taken the opportunity to give Polymer 1.0 a proper test drive. The question I was asking myself: can I get all these goodies without making users pay a huge performance cost? 13 | 14 | I’ll be blunt about my feelings on Polymer 0.5, which I considered a framework: it gave me all the wrong feels. It tried to do so much, and in one go, and it like eating a 5 course dinner when all you wanted was a salad. After all, there’s no hard requirement to make your own elements. Semantic markup does just fine, and it’s hard to beat the browser at components that its engineers have had years to refine. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/polymer-in-legacy-production.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer in Production 3 | authors: [gerwin_sturm] 4 | date: 2017-03-16 5 | original_date: 2017-03-13 6 | link: https://codingwithgerwin.blogspot.com.au/2017/03/polymer-in-production.html 7 | category: articles 8 | --- 9 | 10 | Gerwin provides insight on how to bring web components & Polymer to a large legacy application. 11 | 12 | 13 | -------------------------------------------------------------------------------- /documents/articles/polymer-testing-tips.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer Testing Tips 3 | authors: [maurizio_mangione] 4 | date: 2016-01-05 5 | original_date: 2016-01-05 6 | image : polymer-testing-tips.jpg 7 | link: https://medium.com/google-developer-experts/polymer-testing-tips-f217ba94a64 8 | category: articles 9 | layout: single 10 | tags: ['Polymer', 'Testing'] 11 | --- 12 | 13 |

This article goes through some of the more advanced topics such as user interaction simulation, automatic testing with Continuous Integration, testing on multiple OS/browsers, and more useful tips.

14 | 15 | -------------------------------------------------------------------------------- /documents/articles/polymer-to-create-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Using Polymer to Create Web Components 3 | authors: [rey_bango] 4 | date: 2014-03-31 5 | original_date: 2014-03-31 6 | link: http://code.tutsplus.com/tutorials/using-polymer-to-create-web-components--cms-20475 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | Building modern web applications requires a lot of tooling. This includes preprocessors, JavaScript frameworks, testing tools and a whole lot more. And as the complexities of these apps increases, so does the breadth of tooling and services needed to manage them. Wouldn't it be great if some things were simplified? 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/polymer-unit-testing.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer Unit Testing 3 | authors: [maurizio_mangione] 4 | date: 2015-08-14 5 | original_date: 2015-08-14 6 | image : polymer-unit-testing.jpg 7 | link: https://medium.com/@granze/polymer-unit-testing-d6a69910dc31 8 | category: articles 9 | layout: single 10 | tags: ['Polymer', 'Testing'] 11 | --- 12 | 13 | In the front-end world, testing is a weird topic. Developers know how much testing is important, but lots of them don’t 14 | embrace this practice. This is because testing is often perceived as a time consuming and a difficult task. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/polymer-vs-x-tag-here-is-the-difference.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer vs. X-Tag - Here's the difference 3 | authors: [pascal_precht] 4 | date: 2014-07-29 5 | original_date: 2014-07-29 6 | link: http://pascalprecht.github.io/2014/07/21/polymer-vs-x-tag-here-is-the-difference/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'X-Tag'] 10 | --- 11 | 12 | Let's face it. Web Components is the next big thing. Sure, technologies have to be adapted and implemented by browsers first, but we are on the right track. There was an article recently popping up in the interwebs about Polymer vs. Angular and the differences between those two projects. While it's fairly easy to understand the differences between those two, it's a bit harder to grasp the different directions and approaches of Polymer in comparison to X-Tag, because both seem to provide a solution for building custom web components. This article explains the difference between Polymer and X-Tag. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/polymer-web-components-with-marionettejs.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Polymer Web Components with Marionette.js 3 | authors: [jeremy_fairbank] 4 | date: 2015-01-09 5 | original_date: 2015-01-03 6 | link: http://blog.jeremyfairbank.com/javascript/polymer-web-components-with-marionette-js/ 7 | category: articles 8 | layout: single 9 | tags: ['Interoperability', 'Polymer', 'Marionette.js'] 10 | --- 11 | 12 | JavaScript is a playground. If you disagree, then I encourage you to read Atwood’s Law. A quick Google search will reveal the law in full force with assemblers, machine emulators, and programming languages all written in JavaScript. That is just a small sampling. Go peruse the npm registry for plenty of build tools, frameworks, and servers written in JavaScript. We are tinkerers, especially in the JavaScript community. Sometimes our creations are practical and sometimes they are just fun. 13 | 14 | With that introduction framing this post, I would like to show off some fun I had with [Polymer](http://polymer-project.org/) and [Marionette.js](http://marionettejs.com/) recently. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/practical-questions-around-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Practical Questions around Web Components 3 | authors: [ian_feather] 4 | date: 2015-06-19 5 | original_date: 2015-06-19 6 | link: "http://ianfeather.co.uk/practical-questions-around-web-components/" 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements'] 10 | --- 11 | 12 | Components allow us to build simpler applications by composing independent parts into a greater system. Good component design means you should only need to focus on one component at a time, holding less information in your active mind in order to complete a task. This gives you more mental capacity to focus on the task at hand and ultimately make better decisions. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/principles-for-general-purpose-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Ten Principles for Great General-Purpose Web Components 3 | authors: [jan_miksovsky] 4 | date: 2014-06-13 5 | original_date: 2014-06-10 6 | link: https://github.com/basic-web-components/components-dev/wiki/Ten-Principles-for-Great-General-Purpose-Web-Components 7 | category: articles 8 | layout: single 9 | tags: ['Best Practices'] 10 | --- 11 | 12 | Creating really good general-purpose components entails more work than creating components for a single organization or product. To create components that measure up to the gold standard of the built-in HTML elements, your component will need to be useful right out of the box, work in a wide variety of circumstances, be composable into other components, and more. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/quick-trick-using-template-to-delay-loading-of-images.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Quick Trick: Using Template to Delay Loading of Images 3 | authors: [christian_heilmann] 4 | image: quick-trick-using-template-to-delay-loading-of-images.jpg 5 | date: 2015-09-08 6 | original_date: 2015-09-08 7 | link: http://christianheilmann.com/2015/09/08/quick-trick-using-template-to-delay-loading-of-images/ 8 | category: articles 9 | layout: single 10 | tags: ['template'] 11 | --- 12 | 13 | When it comes to newer elements to play with there are a few that are slightly odd. Canvas is one of them, as it doesn’t do anything without scripting. It is a placeholder for a canvas painting or animation and can contain fallback content when it is not supported. Template is another such element that needs to be addressed in this way. 14 | 15 | 16 | -------------------------------------------------------------------------------- /documents/articles/sane-usage-of-custom-elements.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sane usage of Custom Elements 3 | authors: [lucas_mazza] 4 | date: 2015-09-25 5 | original_date: 2015-09-22 6 | link: http://lucasmazza.github.io/custom-elements.html 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements'] 10 | --- 11 | 12 | Web Components have been an controversial subject that surfaced the Front end world over the last years that I'm still pretty skeptical about its usage on existing and greenfield projects due the lack of good examples on how they can be rolled out to production, but there is sure a way to get started with them without buying in all the hype. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/server-side-web-components-how-and-why.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Server-side Web Components: How and Why? 3 | authors: [jordan_last] 4 | date: 2016-07-13 5 | original_date: 2016-07-13 6 | link: https://scotch.io/tutorials/server-side-web-components-how-and-why 7 | category: articles 8 | layout: single 9 | tags: ['Templates', 'Server Side', 'HTML Imports', 'Shadow DOM', 'Custom Elements'] 10 | --- 11 | 12 | Currently Web Components greatest use cases have been in front end web development. What about the back end? It turns out that Web Components are not only useful for the browser but they are also useful for raw functionality. This article talks about the key benefits in having Server Side Web Components. 13 | -------------------------------------------------------------------------------- /documents/articles/setting-up-your-production-ready-polymer-1-0-application-development.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Setting up your Production-ready Polymer 1.0 Application Development 3 | authors: [ajit_kumar] 4 | date: 2015-07-01 5 | original_date: 2015-06-29 6 | link: http://blogs.walkingtree.in/2015/06/29/setting-up-your-production-ready-polymer-1-0-application-development/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | Any technology we choose to build our project, it is very important that our project lifecycle is managed with effective set of tools that make our overall project development efficient. Depending upon the technology, it may take a while, initially, to set it up but once it is in place, the benefit of it cannot be undermined. Besides, it gives you the much needed agility when it comes to releasing quality code, frequently. 13 | 14 | In this article, we are going to run through the different stages of a project life-cycle for a Polymer 1.0 project and talk about the related tools that can help you run the project, efficiently. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-101.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Shadow DOM 101 3 | authors: [dominic_cooney] 4 | date: 2014-01-19 5 | original_date: 2013-01-04 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom/ 7 | category: articles 8 | layout: single 9 | tags: ['Shadow DOM'] 10 | --- 11 | 12 | Web Components is a set of cutting edge standards. Does this mean you have to decide when to use HTML/JavaScript, and when to use Web Components? No! HTML and JavaScript can make interactive visual stuff. Widgets are interactive visual stuff. It makes sense to leverage your HTML and JavaScript skills when developing a widget. The Web Components standards are designed to help you do that. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-201-css-and-styling.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Shadow DOM 201: CSS and Styling 3 | authors: [eric_bidelman] 4 | date: 2014-01-19 5 | original_date: 2013-03-15 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201/ 7 | category: articles 8 | layout: single 9 | tags: ['Shadow DOM', 'Styling'] 10 | --- 11 | 12 | Let's face it. There's nothing sexy about unstyled markup. Lucky for us, the brilliant folks behind Web Components foresaw this and didn't leave us hanging. We have many options when it comes to styling content in a shadow tree. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-301-advanced-concepts-and-dom-apis.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Shadow DOM 301: Advanced Concepts & DOM APIs 3 | authors: [eric_bidelman] 4 | date: 2014-01-19 5 | original_date: 2013-03-21 6 | link: http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-301/ 7 | category: articles 8 | layout: single 9 | tags: ['Shadow DOM'] 10 | --- 11 | 12 | If you're hosting a party, it gets stuffy if everyone is crammed into the same room. You want the option of distributing groups of people across multiple rooms. Elements hosting Shadow DOM can do this too, that is to say, they can host more than one shadow root at a time. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-custom-elements-update.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Update on standardizing Shadow DOM and Custom Elements 3 | authors: [anne_van_kesteren] 4 | date: 2015-07-29 5 | original_date: 2015-07-28 6 | link: https://annevankesteren.nl/2015/07/shadow-dom-custom-elements-update 7 | category: articles 8 | layout: single 9 | tags: ['Browser Support'] 10 | --- 11 | 12 | There has been revived interest in standardizing shadow DOM and custom elements across all browsers. To that end we had a bunch of discussion online, met in April to discuss shadow DOM, and met earlier this month to discuss custom elements. There is agreement around shadow DOM now. `host.attachShadow()` will give you a `ShadowRoot` instance. And `` elements can be used to populate the shadow tree with children from the host. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-strategies-in-angular-2.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Shadow DOM Strategies in Angular 2 3 | authors: [pascal_precht] 4 | date: 2015-06-29 5 | original_date: 2015-06-29 6 | link: http://blog.thoughtram.io/angular/2015/06/29/shadow-dom-strategies-in-angular2.html 7 | category: articles 8 | layout: single 9 | tags: ['Angular', 'Shadow DOM'] 10 | --- 11 | 12 | Angular 2 has been rewritten from scratch to take advantage of a lot of new technologies that are coming to the web. One of those technologies are Web Components. In fact, Web Components is a set of four technologies: HTML Imports, Templates, Shadow DOM and Custom Elements. Angular uses templates for structural DOM changes, and Shadow DOM for styles and DOM encapsulation. This article explores Angular 2's Shadow DOM emulations and how we can use it. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/shadow-dom-the-basics.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Shadow DOM: The Basics 3 | authors: [rob_dodson] 4 | date: 2014-01-19 5 | original_date: 2013-08-27 6 | link: http://robdodson.me/blog/2013/08/27/shadow-dom-the-basics/ 7 | category: articles 8 | layout: single 9 | tags: ['Shadow DOM'] 10 | --- 11 | 12 | Today, we’ll get our hands dirty with some code! By the end of this post, you’ll be able to create your own encapsulated widgets that pull in content from the outside world and rearrange their bits and pieces to produce something wholly different. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/sharing-styles-across-web-components-with-polymer-and-core-style.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Sharing styles across Web Components with Polymer and core-style 3 | authors: [pascal_precht] 4 | date: 2014-09-30 5 | original_date: 2014-08-01 6 | link: http://pascalprecht.github.io/2014/08/01/sharing-styles-across-web-components-with-polymer-and-core-style/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'Styling'] 10 | --- 11 | 12 | One of the bigger challenges that come with Web Components, is the way how we share common stylesheets across multiple components. Usually, when you build an app and you have styles that are shared along several parts of your code, all you have to do is to is to embed your collected shared styles in your application once, because that's it, right? So you probably have a build process that first pre-processes your stylesheets, concatenates them to one file and if you're good, that file gets minified. Great. But does that work for Web Components too? 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/styling-web-components-using-a-shared-style-sheet.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Styling Web Components Using A Shared Style Sheet 3 | authors: [steven_lambert] 4 | date: 2016-12-15 5 | original_date: 2016-12-15 6 | image: styling-web-components-using-a-shared-style-sheet.png 7 | link: https://www.smashingmagazine.com/2016/12/styling-web-components-using-a-shared-style-sheet/ 8 | category: articles 9 | --- 10 | 11 | Web components are an amazing new feature of the web, allowing developers to define their own custom HTML elements. When combined with a style guide, web components can create a component API, which allows developers to stop copying and pasting code snippets and instead just use a DOM element. By using the shadow DOM, we can encapsulate the web component and not have to worry about specificity wars with any other style sheet on the page. 12 | 13 | 14 | -------------------------------------------------------------------------------- /documents/articles/taming-polymer-with-systemjs-and-typescript-part-1.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Taming Polymer with SystemJS and TypeScript, part 1 3 | authors: [juha_jarvi] 4 | date: 2015-08-27 5 | original_date: 2015-08-27 6 | link: http://blog.charto.net/typescript/Taming-Polymer-with-SystemJS-and-TypeScript-part-1/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer', 'TypeScript', 'HTML Imports'] 10 | --- 11 | 12 | Web Components are awesome for building web apps out of interoperable widgets. They’re made out of 4 technologies which 13 | Polymer 1.0 brings to all major web browsers using polyfills. However one of them, HTML Imports, is so problematic that 14 | Mozilla refuses to implement it natively. Let’s work around it using SystemJS and discover a whole new and (in my opinion) 15 | nicer way of working with Polymer! 16 | 17 | 18 | -------------------------------------------------------------------------------- /documents/articles/the-difference-between-polymer-and-angular.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Here's the difference between Polymer and Angular 3 | authors: [alex_mingoia] 4 | date: 2014-07-08 5 | original_date: 2014-06-24 6 | link: http://www.binpress.com/blog/2014/06/26/polymer-vs-angular/ 7 | category: articles 8 | layout: single 9 | tags: ['Angular', 'Polymer'] 10 | --- 11 | 12 | A year after pulling back the curtains on the Polymer Project, Google’s taken part of I/O 2014 to demo what the code can do. Right on cue, the web is abuzz with discussion comparing Polymer to other popular web frameworks, and it’s no surprise since it bears some resemblance to Google’s very own AngularJS. Join me after the break as I introduce Polymer and explore just how it relates to Angular. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/the-state-of-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: The state of Web Components 3 | authors: [wilson_page] 4 | date: 2015-06-10 5 | original_date: 2015-06-09 6 | link: https://hacks.mozilla.org/2015/06/the-state-of-web-components/ 7 | category: articles 8 | layout: single 9 | tags: ['Browser Support'] 10 | --- 11 | 12 | Web Components have been on developers’ radars for quite some time now. They were first introduced to the world at Google IO 2011. The concept shook the community up and became the topic of many future talks and discussions. 13 | 14 | By now, 4 years on, Web Components should be everywhere, but in reality Chrome is the only browser with ‘some version’ of Web Components. Even with polyfills it’s clear Web Components won’t be fully embraced by the community until the majority of browsers are on-board. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/there-is-an-element-for-that.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: There is an Element for That 3 | authors: [sebastian_henneberg] 4 | date: 2015-09-19 5 | original_date: 2015-09-19 6 | image: there-is-an-element-for-that.jpg 7 | link: https://medium.com/@sebastianhenneberg/there-is-an-element-for-that-a9fcdafe4a25 8 | category: articles 9 | layout: single 10 | tags: ['Polymer'] 11 | --- 12 | 13 | Sebastian attended to the first ever Polymer Summit in Amsterdam recently. This was his first Polymer conference obviously but this was also his first conference & trip to Amsterdam. As an AngularJS developer he was very curious about the Polymer Project and the ambitious ideas behind it. Here is what he had to say. 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/turn-your-phone-into-a-motion-controller-with-polymer.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Turn Your Phone into a Motion Controller with Polymer 3 | authors: [kevin_gleason] 4 | date: 2015-06-17 5 | original_date: 2015-06-17 6 | image : turn-your-phone-into-a-motion-controller-with-polymer.jpg 7 | link: http://www.pubnub.com/blog/turn-your-phone-into-a-motion-controller-with-polymer/ 8 | category: articles 9 | layout: single 10 | tags: ['Polymer', 'Custom Elements'] 11 | --- 12 | 13 | With a realtime bidirectional data channel, we have to the power to make our devices interact with one another. As a result, 14 | this has opened up the doors for more interactive experiences using Web Components & Polymer. 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/universal-web-components.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Universal Web Components 3 | authors: [jordan_last] 4 | date: 2017-03-13 5 | original_date: 2017-03-06 6 | link: https://scotch.io/bar-talk/universal-web-components 7 | category: articles 8 | layout: single 9 | tags: ['Custom Elements'] 10 | --- 11 | 12 | Applications built from web components can be easy to understand, grow, and refactor, because they are easy to break up into modular and declarative pieces. They work well in the browser, but I believe there is far greater potential as they begin to spill out of the browser, into the desktop, server, and even embedded applications. 13 | -------------------------------------------------------------------------------- /documents/articles/upgrading-from-polymer-0-5-to-1-0.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Upgrading from Polymer 0.5 to 1.0 3 | authors: [josh_crowther] 4 | date: 2015-06-01 5 | original_date: 2015-06-01 6 | link: http://jcrowther.io/2015/06/01/upgrading-from-polymer-v0-5-v1-0/ 7 | category: articles 8 | layout: single 9 | tags: ['Polymer'] 10 | --- 11 | 12 | Last week I was able to attend a Google I/O extended in Bluffdale Utah and it was awesome. There were a ton of cool things announced in the Android space but for me the best part was, by far, the announcing of Polymer 1.0! 13 | 14 | I recently went through the process of upgrading one of my applications (yes, I know the announcement was two days ago... I was excited) and wanted to share some of my learnings as well as the steps I took. This 15 | 16 | 17 | -------------------------------------------------------------------------------- /documents/articles/using-polymer-1-0-with-angular.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Using Polymer 1.0 with Angular 3 | authors: [josh_crowther] 4 | date: 2015-06-01 5 | original_date: 2015-05-26 6 | link: http://jcrowther.io/2015/05/26/using-polymer-webcomponents-with-angular-js/ 7 | category: articles 8 | layout: single 9 | tags: ['Angular', 'Polymer'] 10 | --- 11 | 12 | Polymer and Angular.js are two incredibly popular projects that are run by Google. The two projects serve different purposes yet can, with some coercion, be made to work together. Eric Bidelman, a dev from the Polymer team, made a great youtube video on this (which can be found [here](https://www.youtube.com/watch?v=p1NpZ-0Op0w)) and I wanted to give another example of the two projects working side-by-side. 13 | 14 | 15 | -------------------------------------------------------------------------------- /documents/articles/web-component-challenges.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Web component challenges 3 | authors: [leon_revill] 4 | image: web-component-challenges.png 5 | date: 2016-06-28 6 | original_date: 2016-06-17 7 | link: https://blog.revillweb.com/web-component-challenges-a09ebc598d65#.oacfju67t 8 | category: articles 9 | layout: single 10 | tags: ['ES2015', 'Components', 'Challenges'] 11 | --- 12 | 13 |

People still seem wary of making use of web components because they are new, some of the standards are still in flux and there is yet to be a solid set of best practices discovered. Because of this I thought it best to address some of the issues head on and offer some solutions.

14 | 15 | -------------------------------------------------------------------------------- /documents/articles/web-components-accessibility-and-the-priority-of-constituencies.html.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Web Components, accessibility and the Priority of Constituencies 3 | authors: [bruce_lawson] 4 | date: 2015-04-24 5 | original_date: 2015-04-23 6 | link: http://www.brucelawson.co.uk/2015/web-components-accessibility-and-the-priority-of-constituencies/ 7 | category: articles 8 | layout: single 9 | tags: ['Accessibility', 'Community'] 10 | --- 11 | 12 | Gosh, what a snappy title. I’m not expecting a job offer from Buzzfeed any time soon. 13 | 14 | Today, Apple sent their [consolidated feedback on Web Components](https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0225.html) to the webapps Working Group. The TL;DR: they like the concept, are “considering significant implementation effort”, but want lots of changes first including [removal of subclassing](https://www.w3.org/Bugs/Public/show_bug.cgi?id=28547), eg `