Component

Buttons, form fields, cards, navigation items and dialogs are common components. Design tools and codebases often use component libraries to keep repeated UI consistent. In practical terms, Component belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Component as if it also meant Design System. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Make the component reusable around a clear purpose; too many one-off options turn it into another unstructured page template.

In day-to-day work, Component matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A card component might define image, title, metadata and action regions with documented variants and responsive behavior. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.