Web components
Shadow DOM styling
mdn/web-components-examples: A series of web components examples, related to the MDN web components documentation at https://developer.mozilla.org/en-US/docs/Web/Web_Components.
A series of web components examples, related to the MDN web components documentation at https://developer.mozilla.org/en-US/docs/Web/Web_Components. - mdn/web-components-examples: A series of web c...
Web Components
Stencil
Build. Customize. Distribute. Adopt.
Truly Portable Patterns
HTML Web Components Are Having a Moment
Everyone’s talking about HTML Web Components, and I think it’s the start of something magical!
daviddarnes's list / 🧱 Web Components
Anything to do with Web Components
Web Components Eliminate JavaScript Framework Lock-in | jakelazaroff.com
Web components can dramatically loosen the coupling of JavaScript frameworks. To prove it, we're going to do something kinda crazy: build an app where every single component is written in a different JavaScript framework.
Just-in-Time JavaScript – David Bushell – Freelance Web Design (UK)
The one where I render JavaScript on the fly
006: “Shadow dom is not a good default” • Buttondown
Friends! Last week I rambled out loud about web components and how their true magic lies in extending HTML. Heck, Jeremy even called them “HTML web...
An Attempted Taxonomy of Web Components—zachleat.com
A post by Zach Leatherman (zachleat)
Building Interoperable Web Components That Work | CSS-Tricks
This post will show you how to build low-level UI web components once, in a framework-agnostic way, and then re-use them between frameworks
3 Approaches to Integrate React with Custom Elements | CSS-Tricks
In my role as a web developer who sits at the intersection of design and code, I am drawn to Web Components because of their portability. It makes sense:
Web Components Guide
The Guide to Web Components
Bauteile | Articles | web.dev
Komponenten sind die Bausteine moderner Webanwendungen. Welche Best Practices sollten Sie beim Erstellen Ihrer eigenen Komponenten befolgen, damit diese auch die Zeit überdauern?
Remix - Build Better Websites
Remix is a full stack web framework that lets you focus on the user interface and work back through web standards to deliver a fast, slick, and resilient user experience. People are gonna love using your stuff.
Ornament - Eine Web-Component-Microlibrary • Peter Kröner • Webtechnologie
HTML Web Components: An Example
Writing about the big beautiful mess that is making things for the world wide web.
Shadow DOM on Regular Elements
For some reason, I had this misconception that Shadow DOM could not be used with regular elements, I only ever tried it with the custom ones.
Blinded By the Light DOM – Eric’s Archived Thoughts
The web home of Eric A. Meyer, CSS guy; and his wife Kathryn, doctor of nursing.
GitHub - davatron5000/awesome-standalones: A curated list of awesome framework-agnostic standalone web components
A curated list of awesome framework-agnostic standalone web components
Writing Components That Work In Any Frontend Framework
browser-window Web Component—zachleat.com
A post by Zach Leatherman (zachleat)
Adactio: Journal—HTML web components
Donât replace. Augment.
Web Components Will Outlive Your JavaScript Framework | jakelazaroff.com
If we're building things that we want to work in five or ten or even 20 years, we need to avoid dependencies and use the web with no layers in between.
So verwendet Nordhealth benutzerdefinierte Eigenschaften in Webkomponenten | Articles | web.dev
Die Vorteile der Verwendung benutzerdefinierter Eigenschaften in Designsystemen und Komponentenbibliotheken.
Live office hours: Web Components and Lit
There's a growing buzz about building with Web Components. And Lit is emerging as a popular way to help developers do that. But Phil doesn't know much about ...
heybran/web-components-resources
Contribute to heybran/web-components-resources development by creating an account on GitHub.
Truly Portable Design Patterns
Components are everywhere, but they are rarely reusable across systems. A design system component is written differently than a CMS editor component. But does it have to be this way? Could we take one set of components and port them to multiple JavaScript frameworks, import them into design tools, and use them for the editing…