Inclusive development through web components
summary
Claims that a single web‑component library can replace framework duplication and integrate with existing toolchains while preserving design‑system parity. Uses Stencil to compile components and output React, Vue, and Angular wrappers and wires them into Code Connect. Notes a surprising stat — 52% of front‑end jobs require React — and demonstrates a concrete refactor: Figma’s Simple Design System converted to web components with code snippets and Code Connect support, launched and working across frameworks.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:56Modern web evolution
- 7:29Framework fragmentation
- 8:33Web components benefits
- 10:40Live demo: web component
- 13:11Raw component limits
- 15:15Stencil for limitations
- 18:27One codebase unified
- 19:29SDS refactor example
- 20:34Future of inclusive web
related talks
22m'Centralizing the Frontend with Design Systems and Web Components'
56mChasing the holy grail Reusable Web Components and Design Tokens
16mScaling Components Across Multiple Frameworks
20mMake Web Components Great Again with StencilJS
20mAvoiding vendor lock-in through Web Components
52mWeb Components Can Do That?
41mDemystifying Web Components as the Weapon for Web
33mWeb Components with StencilJS