Practice design system governance vocabulary: breaking changes, component APIs, deprecation, migration sprints, and component library management.
0 / 5 completed
1 / 5
A '_____ change in the component API' means existing code using that component will break after the update.
A 'breaking change' changes the component's interface in a way that is not backward-compatible — consumer code must be updated to work with the new version.
2 / 5
'We're _____ the old Button component.' What does this mean for the component?
'Deprecating' a component signals it will be removed in a future version. It still works but engineers are warned to migrate away from it.
3 / 5
'Consumer teams have 2 _____ to migrate.' What unit of time is used?
'2 sprints to migrate' gives consumer teams a concrete, agile-aligned window (typically 2-4 weeks) to update their code before the old component is removed.
4 / 5
'The design system team _____ all new components.' What is their role in governance?
The design system team reviews proposed new components to ensure consistency, reusability, and alignment with system principles before they are added.
5 / 5
'This pattern is in the _____ library.' Where are reusable UI components stored?
The 'component library' is the shared repository of reusable UI components in the design system, accessible to all product teams.