Frontend denotes the layer of an application that interacts with users, covering presentation and client-side logic. It combines UX design, performance optimization and interfaces to backend services and influences development and operational decisions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Frontend is the application layer that interacts with people in the browser or another client environment. It combines presentation, input handling, and client-side logic with browser capabilities and backend services.
As web software moved from static pages to interactive applications, the visible user interface had to be organized as its own layer. The frontend field emerged around HTML for structure, CSS for presentation, and JavaScript for behavior, handling input in the browser, updating views, and relying on standards and browser APIs.
Think of the frontend as the working layer between people and the system. HTML provides structure, CSS shapes the interface, JavaScript reacts to events, and the DOM keeps the current page mutable. Data often arrives asynchronously from services, is translated in the browser into state and components, and is then rendered again. Strong frontends balance usability, response time, and device diversity.
HTML defines the structure, meaning, and hierarchy of the content that makes up the interface.
CSS controls layout, typography, colors, and adaptation to different screen sizes.
JavaScript handles events, synchronizes state, and implements client-side logic in the browser.
The DOM is the mutable representation of a view that scripts and browsers work against.
Accessibility ensures the interface works with keyboard use, assistive technologies, and clear semantics.
Backend APIs supply data and actions that the frontend incorporates into the user interface.
Frontend knowledge helps shape, build, and evaluate web and app interfaces. It is especially important for architecture, framework, accessibility, and performance decisions. Limits come from browser differences, loading time, and dependence on interfaces; more interactivity often also means more complexity and maintenance effort.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.