Preliminary, experimental, incomplete, undocumented, and generally unsuitable for anything. Expect everything to change.

Tiny function library useful for Custom Elements.

Custom Elements depend on bits of the Web Components standard platform itself. Specifically, CustomElements and HTMLImports feature support is expected.

These features are natively available in Chrome, and otherwise supported by web-componentsjs polyfills. These elements do not depend on ShadowDOM, so webcomponents-lite is sufficient.

In all their aspects, including shadow-dom and the new recruit, css property-bags.

Nuf said.

Large-scale reuse and sharing, utilize existing DOM contract.

Use the Web Platform, embrace the DOM, avoid abstracting the surface or using as render-target.

• Payload Size
• Time To First Paint (TTFP)
• RAIL

• Deep linking
• i18n
• a11y
• Polish
• Animation
• Offline/Progressive/Applike (Fizzy)

• KISS
• DRY
• Reuse

• KISS
• Be nimble
• Be expressive
• Be readable
• Be robust

Custom Elements exposes DOM's fundamental power as a component-model. Component power enables us to surmount the Web App needs in a satisfying manner.

Once making scoping work is less of a burden, it'll be easier to grasp the usefulness of the deep interoperability afforded by Shadow DOM. At that time the large-scale sharing afforded by the pure element interface will be attractive.