Skip to content

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

Description

@JedWatson

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions