Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pros and cons of one-or-many-package publishing of design system components #14

Open
JedWatson opened this issue Nov 8, 2019 · 0 comments

Comments

@JedWatson
Copy link
Member

There are pretty significant downstream implications of how design systems are published - whether they're a single package for all components (e.g Material UI), a package for each component (e.g Atlaskit) or a few packages for groups of components (e.g Blueprint)

We should document the pros and cons we've learned of each, and how this relates to release cadence as well (#13). This is probably not a one-size-fits-all thing across design systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant