Web Components

Paul Kinlan June 27 2022

I use logseq to journal what I learn and read. These are the wiki pages for my knowledge graph and are intended to just be bullet points that I use for further thinking and quick reference.

Usage on the wild
- Github: How we use Web Components at GitHub | The GitHub Blog
- Stripe: Embeddable pricing table for SaaS businesses | Stripe Documentation
- Photoshop: Photoshop's journey to the web
Libraries Tools
- Lightning Web Components: Component Library / https://lwc.dev/
- Minze: Minze, a Minimalistic JS Library for Creating Web Components
- Infragistics: Web Components |100+ UI Components | Infragistics
- Lit: Lit
- Catalyst: Introduction - Catalyst
- Spectrum: Spectrum Web Components by Adobe
Custom Elements Everywhere
- This project runs a suite of tests against each framework to identify interoperability issues, and highlight potential fixes already implemented in other frameworks. If frameworks agree on how they will communicate with Custom Elements, it makes developers' jobs easier; they can author their elements to meet these expectations.
webcomponents.org - Discuss & share web components

View Source | Make a correction | Correction history

About Me: Paul Kinlan

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.

Mastodon Book a consultation