Define boundaries on balancing when components are added to the library versus being “standalone”, built as “one-off” component.
Compare decision point in Governance model.
Things to consider:
- General application possible (example: button) versus specific to one context, one team, one problem
- Being an addition, a variant to an existing component vs. single component
Decision guardrails to above:
- Possible performance impact on library (eventually countered with entry points to the library, compare T280828 or longer-term abilities like tree-shaking)
- Possible maintenance burden on DS team, not on feature team, ever-growing backlog