Web Components

preview_player
Показать описание
Web Components are a polarizing feature that seem simultaneously old news and not quite ready for production yet. But we’ve been making things with Web Components, and finding some areas where they really work well. Join us to hear more about how we’re using them, what they work well for, and why we’re excited about them.

- When did Web Components “click”
- How to incorporate progressive enhancement
- Future Web Components projects
- What is still missing from Web Components?
- Thoughts on lit

Links and Demos:
Slide-deck

Ground control

is-land

fundraising-status

An Attempted Taxonomy of Web Components

Progressive Enhancement Recipes using Eleventy WebC Image Comparison Components -

Zach Leatherman

I Need Your Help to Make 11ty Fully Independent and Sustainable in 2024

Eleventy

Рекомендации по теме
Комментарии
Автор

Miriam and Zach are going to build a W3C Web Annotation Web Component; that's what I heard — I'm definitely not misconstruing what has been said here. All we need to do is find unlimited resources.

Great conversation. I like the idea of a web component taxonomy as well as differentiating between standalone custom elements — meant to be available to every website — and bundles of custom elements with shared dependencies coming from design systems — meant to be used together.

tobiasfedder
Автор

If I understand it correctly, to use a custom element (say web component) that I created, doesn't the browser have to download extra JS code and register it using DOM API (that is JS, again)? How is this better when it comes to loading performance than using a React component?

zettadam