/explore
|
You are here 
|
www.petergoes.nl | ||
| | | | |
www.voorhoede.nl
We did an experiment: create and consume a Web Component using a selection of JavaScript frameworks. In this post we'll share our experience and our verdict. |
|
| | | | | ||
| | | | |
matuzo.at
I'm a frontend developer, consultant, accessibility auditor, blogger, teacher, and book author from Austria. |
|
| | | | | ||
| | | | |
blog.damato.design
Passively requesting code once an element is discovered on a page. |
|
| | | | | ||
| | | | |
lea.verou.me
When developing customizable components, one often wants to expose various parameters of the styling as custom properties, and form a sort of CSS API. This is still underutlized, but there are libraries, e.g. Shoelace, that already list custom properties alongside other parts of each component's API (even CSS parts!). Note: I'm using "component" here broadly, as any reusable chunk of HTML/CSS/JS, not necessarily a web component or framework component. What we are going to discuss applies to reusable chunks of HTML just as much as it does to "proper" web components. Let's suppose we are designing a certain button styling, that looks like this: We want to support a -color custom property for creating color variations by setting multiple things internally: .fan... |
|
| | | |||
