PatternFly Elements - A Performant Design System
summary
PatternFly Elements 2.0 implements PatternFly visuals as web components so any stack can use them; components are authored with TypeScript + Lit and PatternFly design tokens, support slots and attributes, and aim for a one-to-one visual match with PatternFly React. A demo shows 222 KB vs 2.5 MB of JavaScript (web components vs CRA React) and pages render with no-JS. CDN + import maps distribution works; server-side rendering uses declarative Shadow DOM and form handling relies on form-associated custom elements; Red Hat Design System applies branding and microfrontends use elements successfully.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:36What are Web Components
- 1:55Web Component Core Technologies
- 3:50What can you Build with Web
- 4:41Advantages of Web
- 7:54A Brief History
- 10:37PatternFly Elements 2.0
- 13:39Making PatternFly Elements
- 16:06Getting PatternFly Elements
- 17:25Using Pattern Fly Elements
- 20:39The Future
- 22:57Why Two Design Systems?
- 24:02Case Study
related talks
39mStyling a design system based on Bootstrap 4 and Web Components
21mComponent-based Design System and Development
35mDesign system - From a Developer Point-of-View
56mChasing the holy grail Reusable Web Components and Design Tokens
26mComponents, Patterns and sh*t it’s Hard to Deal with
41mHigh-Performance Web UI with Web Components
30mDesigning with React
44mFostering Collaboration: Pattern Libraries / Rapid Prototyping
