Component library
A component library brings together reusable interface elements. Behaviour, variants and the right version also matter when using them.
A component library is a collection of reusable interface elements, such as buttons, input fields or dialogs. It can provide design templates, code and related documentation; not every collection contains all of these parts.
Reuse a component for a specific purpose
In a fictional project portal, the request form and profile settings use the same Save button. The shared appearance is only reliably helpful if the required states and behaviour also fit. A suitable icon alone says nothing about loading, keyboard interaction or the response to an error.
Connect the collection with rules for use
Carbon presents components as designed and coded solutions to specific interface tasks. For your own product, also establish which version is used and when an existing variant fits. A library does not replace that decision. Check reused components within their respective workflows; a shared origin does not prove that every assembled page works correctly.
Sources
Related terms
- Design handoffA design handoff passes a design on for implementation. States, behaviour and outstanding decisions need to be clear.
- Component variantA component variant is a defined form of a shared building block. It differs from a temporary interaction state.
- UI componentA UI component is a reusable part of a user interface. Its purpose determines the presentation and interaction behaviour it needs.
- Design tokenA design token stores a named design decision. Multiple components can use it, allowing a value to be changed in a defined place.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.