Web Components, Shadow DOM, and Custom Element related posts

27
Likes
+0
Growth per month

In the feed right now

Live from Bluesky
Gordon @gordon.bsky.social · about 13 hours ago
Very nice! Would be amazing to have an unstyled web component lib with the same level of coverage as Base UI.
Replies0 Reposts0 Likes0
Serhii Kulykov @iamkulykov.bsky.social · about 13 hours ago
A11y Memoirs, episode 2: The Devil is in the Details One line of code can make the difference between an accessible component and a confusing screen reader experience. Lessons learned while building Vaadin details and accordion web components: dev.to/webpadawan/a... #Accessibility #a11y
A11y Memoirs, episode 2. The Devil is in the Details

dev.to

A11y Memoirs, episode 2. The Devil is in the Details

The story of Vaadin Details and Accordion, from shadow DOM roots and an external accessibility audit to one line of code that fixed an NVDA issue.

Replies0 Reposts0 Likes0
riley 🌙 @seventhdawn.etheirys.social · 1 day ago
i tend to find that a lot of carrd templates are SUPER overdesigned and not very intuitive for first time users? and a lot of them also require pro to use (for the custom html elements) so the most important thing imo is finding something that's not too flashy
Replies0 Reposts0 Likes1
Chris Hayes @chris.nutmeg.social.ap.brid.gy · 1 day ago
Anyone building with #11ty use WebC? I've built with 11ty and Lit separetely. Currently considering the best way to build in 11ty with Web Components, and WebC seems the obvious choice, but it has not received a release in 3 years. Not sure if I'm creating tech debt for myself if I go with WebC […]

nutmeg.social

Original post on nutmeg.social

Replies2 Reposts0 Likes1
Aaron Gustafson @aaron-gustafson.com · 1 day ago
You’re always quick with a kind word. I’d be happy to build an article around the component (or one of my other ones) and how to thoughtfully architect progressively-enhanced web components.
Replies1 Reposts0 Likes2
Keep reading on Bluesky