I agree! There is a gap for these as well as for things like design tokens. I know the W3C has the design token spec/schema, but that means we have disperate technologies for different parts of our solution that aren't necessary designed to work together.
That is a very underrated feature!
Yeah, I get it. I think a lot of people were a little turned off by the original home page design initially which made it a little unclear about the open source nature of it.
I like the new design much better now.
webawesome.com
If you're using the Custom JSDoc Tags plugin for your #WebComponents, you can now add them at the property level!
wc-toolkit.com/documentatio...
What's not vibin'?
Yeah, that does look off. Maybe someone at @webawesome.com can take a look.
Introducing Litro - a fullstack framework for Web Components.
File-based routing, SSR + SSG, API routes, Vite HMR.
Basically the Nuxt/Next experience, but you write Lit, FAST Element, or Elena components instead of React/Vue.
#WebComponents #Lit #TypeScript #SSR #OpenSource #WebDev
litro.dev
Come nerd-out with me about #UX!
this is a great CSS read.
blog.gitbutler.com/the-great-cs...
not to mention syntax improvements; nested CSS, CSS vars and mixing colors, et al.
Would this be something that could be used in a data grid scenario?
@infrequently.org might know somebody.
How so? How is security a factor here?
Yeah, I agree that would be important as well and I mention that in the article. Mapping attributes to DOM parts would be a great "phase 2" once that spec gets finalized.
Sure there are! Just a few are:
- I can run them safely in an SSR environment
- I can have them be purely HTML and CSS with no JS required for bootstrapping my components.
I think they can be minimally viable with what I just outlined in the article. Just these features alone would be very beneficial.
When you say "expression language and bindings", is that referring to DOM parts?
DCEs are markup, so they can be added directly to a page. If/when HTML modules are available, you could load them from an external source too. I look forward to that capability as well.
You _can_ use render blocking scripts but that's not always practical, especially when you have a large number of components and components are dynamically loaded using something like a CMS.
I measured using gzip.
When I was at Microsoft, we were trying to find ways around some of the pain points of #WebComponents, so I did an exploration on what Declarative Custom Elements could potentially provide us.
#html #css #javascript
dev.to/stuffbreaker...
I will say I am seriously lacking a sexy RSS feed with my current setup.
Maybe I should fix that... 😆
@davatron5000.bsky.social: "Burton Smith still uses Dev.to for his personal blog".
#webdev #webcomponents #designsystems
Sure! It's pretty easy to try it. The barrier to entry is really low and can run alongside your existing stuff.
Food for thought all you people out there #developingDesignSystems
report.zeroheight.com/
#webDev #webComponentsCG
Wait, @stenciljs.com is web components...
Wait, I thought smart homes and IoT were the dream...
Really? Why?
I had high hopes for WindowsCE. I would still love to see something like this happen.
