And between one-off components and more or less regularly used components there's a gray area where you have to draw a line.
At our design system we often don't add components if they are (and will be) used by one team only. Because then the team is a bigger expert on the component than us.
At our design system we often don't add components if they are (and will be) used by one team only. Because then the team is a bigger expert on the component than us.
Comments
But, where a component may have a use across lots of (even all teams - I’m thinking a button) patterns are likely to be much less. Still multiple teams, but much less.
To really answer your question I just wanted to know what a pattern is to you and what a component is. So that we are not talking about different things…
So I see a component as a single reusable piece of UI that has a generic use (e.g. a date picker), and a pattern is often, but not always, a collection of components that are more specific to meeting a need (e.g. selecting a date and time for an appointment).