A component is a small, contained unit of UI — markup, behavior, and styles bundled behind a single name. Modern web work is, more than anything, the practice of finding the right components and putting them together.
In plain language
On the web, this term comes up when people talk about how pages, apps, and services are built or connected. A component is a small, contained unit of UI — markup, behavior, and styles bundled behind a single name. Modern web work is, more than anything, the practice of finding the right components and putting them together. If you are new to the field, the simplest mental model is this: a reusable piece of interface, with its own state. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of Component as part of the doorway between a person and a machine. People see the door — the page that loads, the button that responds — and barely notice the hinges. Component is one of the hinges.
Where it shows up
You meet Component in almost every website, app, and dashboard. The piece itself is invisible; what you notice is the page that loads, the field that updates, the screen that fits the phone in your hand.
A small example
Imagine the scene above. The role Component plays is the one its blurb describes — A reusable piece of interface, with its own state. Every time a page loads or a button fires a request, ideas like this are quietly doing the work between the browser and the server.
Common misunderstanding
One line to take with you
Component is part of the surface between people and machines. The user sees the result, never the seam.