Wow Michael, so many thoughtful and interesting things you've said. I really appreciate this dialogue! I totally appreciate the notion of cutting scope creeps and prioritizing based on limited resources. It's the world we all live in!

I'm very encouraged by how thoughtfully your write about this, the guides I've found on Svelte Storybook (I literally went "Wow, they've already written this comprehensive of a guide for Svelte!?!"), and the fact that the project is obviously so successful already.

So, interestingly, this conversation and my feelings about the whole ecosystem of design systems and ui components today prompted me to write about it: https://developtodesign.com/design-systems-suck -- no worries I'm not shamelessly plugging I have like 3 readers there so far :-)

But, I make 3 complaints:

1. ui components are too tied to frameworks today 2. tooling for authoring vs. tooling for custom publishing is currently problematic (to a certain degree and per our conversation here)

3. syncing between design and dev never works.

Obviously, those 3 complaints are wide and varying but certainly related to "our world" as design system implementors today. So hard to fix all these!

At the end of the article I basically say I'm going to only focus on 1. for now and hope, no pray that someone else takes care of 2 and 3.

I have to be careful about it all because I'm well aware of motivational and life forces that could prevent me from following through here, but, my raw idea which I've already started to spike on, is that just like Addy Osmani's TodoMVC, we should have an agnostic html/css based framework that has various framework adaptations like /react/button, /svelte/button, /vue/button etc., that all somehow pull from the base html and css, but are adapted to conform to their respective idioms. Having done a lot in the Buttons world I'll start with a single button and see how it goes.

In a lot of ways, the real work of my idea is already done tenfold or more. Materialize, Github's Preset CSS, Bootstrap, and many others already have some great, semantic and bug free html/css. So really, this is more of an organizational and curation idea. I'll let you know if anything happens of it.

But, it's great to know that folks like you care so much about the documentation aspects and again, I really appreciate you dropping by in the comments here to explain the roadmap a bit. It's quite encouraging!

And of course I'll definitely consider Storybook for this if/once I get it up and running...especially since it seems to be the only game in town that actually has documentation and works with many frameworks (I followed along with the Svelte tut I mentioned and, yup, it certainly does work!)