Open Westbrook opened 2 years ago
We are having this very conversation.
I would sum this up as "what is the appropriate API for you?"
I look at Shoelace and I see a wide-open API, but there is the intent that users will want a lot of flexibility in their use. But then I look at what we are doing and we want to support flexibility, but also have consistency to maintain.
Documentation is cool, demos are cool, linting and analysis is cool, what else can a developer of a design system to ensure their consumers are as successful as possible at leveraging the tools they offer?
Customization is cool, but might not be a goal. What if attributes or properties are used incorrectly (particularly those that support things like accessibility), or not at all? Can Dev builds save our souls?