Practice essential collocations for design systems in IT and software development.
0 / 5 completed
1 / 5
The design team worked to ___ consistency across every product surface by sharing a single component library.
Maintain consistency is the standard design system collocation for keeping a uniform look and behaviour across an interface. 'Keep along' and 'hold around' are informal. 'Carry out' refers to performing a task and does not fit this context.
2 / 5
The designers and engineers collaborated to ___ reusable components that any team could drop into their product.
Build components is the standard design system and front-end collocation for constructing reusable interface elements. 'Make along' and 'create around' are informal. 'Put out' has a different meaning and does not fit this context.
3 / 5
The team published clear guidelines to ___ how and when each component should be used.
Document guidelines is the standard design system collocation for formally recording usage rules and best practices. 'Write along' and 'note around' are informal. 'Set out' is acceptable for presenting rules but 'document' is the more precise collocation for a design system.
4 / 5
The design lead worked to ___ design tokens that defined colour, spacing, and typography in a single source of truth.
Define tokens is the standard design system collocation for specifying the named values that drive consistent styling. 'Set along' and 'make around' are informal. 'Lay out' is close but defining tokens is the precise collocation here.
5 / 5
As products evolved, the team had to ___ the component library so it stayed aligned with brand updates.
Update the library is the standard design system maintenance collocation for keeping shared components current. 'Change along' and 'revise around' are informal. 'Fix out' is not a standard phrase in this context.