Terms with relationships

A connected web development glossary

Definitions become useful when they show what a concept controls, which evidence reveals it, and which neighboring concept it can be confused with.

By Web Dev Masters Editorial Team · Published July 22, 2026 · Updated July 23, 2026

Document
Meaning and structure

Runtime
Events and rendering

Network
Requests and caches

Release
Artifact and identity

Most production bugs cross at least two terms; tracing the relationship reveals the owning layer.

Document and presentation terms

Semantic HTML: Markup selected for meaning and behavior rather than appearance. It provides landmarks, headings, native controls, and relationships used by browsers, assistive technology, search systems, and maintainers.
DOM: The live Document Object Model produced when the browser parses markup. JavaScript reads and changes this tree; it is related to but not identical with the original source text.
Source order: The order of nodes in the document. It normally drives reading and keyboard sequence, even when CSS arranges elements differently on screen.
Cascade: The CSS conflict-resolution process considering origin, importance, layer, specificity, scope, and source order. It determines which declared value wins for a property.
Intrinsic sizing: Sizing derived from content and the element’s own constraints, such as minimum content, maximum content, and aspect ratio, rather than a fixed external coordinate.
Container query: A conditional style based on an ancestor container’s size or style, useful when a reusable component should adapt to available space rather than the entire viewport.

See Semantic HTML and Resilient CSS for code examples connecting these terms.

JavaScript and runtime terms

Event: A notification that something occurred, such as activation, input, submission, or network completion. Event type should match user intent rather than one hardware input method.
State: The smallest authoritative data required to explain the current interface. Loading, success, empty, error, and cancellation are distinct states when they produce different user outcomes.
Promise: An object representing eventual completion or failure of an asynchronous operation. It does not make work parallel by itself.
Event loop: The runtime mechanism that schedules tasks and microtasks while coordinating script execution, rendering opportunities, and browser work.
Race condition: A defect where outcome depends on timing or order that the program did not control, such as an old search response overwriting a newer query.
AbortController: A Web API that provides an abort signal to supported operations such as Fetch, allowing work that no longer belongs to the current intent to be canceled.

The JavaScript guide demonstrates cancellation plus a sequence guard.

Accessible name: The text by which assistive technology identifies a control or object. It may come from visible text, a label, alternative text, or an ARIA naming relationship.
Accessibility tree: A platform representation derived from document semantics, styles, and accessibility properties. Assistive technologies use it to understand roles, names, states, and relationships.
Focus: The current target for keyboard input. Focus order, visibility, movement, and return behavior determine whether a task remains predictable.
Keyboard trap: A condition where focus enters an interface region but cannot leave through normal keyboard commands.
ARIA: Roles and attributes that supplement HTML where native semantics are insufficient. ARIA does not automatically add native keyboard behavior.
WCAG: Web Content Accessibility Guidelines developed through W3C, providing testable success criteria organized around perceivable, operable, understandable, and robust content.

Use the accessibility test matrix to turn these definitions into checks.

Performance and HTTP terms

LCP: Largest Contentful Paint, a field metric about when the largest relevant content element in the viewport is rendered.
INP: Interaction to Next Paint, a field metric summarizing page responsiveness across observed interactions.
CLS: Cumulative Layout Shift, a measure of unexpected visual instability during the page lifetime.
Critical path: The dependent work that must finish before an important visual or task milestone can occur.
Private cache: A cache associated with one client, typically the browser, which may store responses that must not be shared among users.
Shared cache: A cache that can reuse responses for multiple clients, including some proxies and managed CDN caches.
Revalidation: A conditional request that asks whether a stored response remains current, often using ETag or Last-Modified validators.
Immutable asset: A resource whose URL identity changes whenever its bytes change, allowing a long freshness lifetime without serving revised content under the same URL.

Build and deployment terms

Build artifact: The packaged output intended for deployment. A reliable workflow creates it once, tests it, records its digest, and promotes the same bytes.
Release manifest: Machine-readable evidence linking an artifact to source commit, build time, runtime requirements, and important asset hashes.
Release: A versioned combination of a build and the configuration needed to run it in an environment.
Deployment: The process of making a release active in a target environment.
Atomic switch: A promotion step where users observe either the complete old release or the complete new release, not a partially copied mixture.
Health check: An endpoint or probe reporting process and dependency status. A status response should include nonsecret release identity when used for deployment verification.
Smoke test: A small production-oriented check of the public path and critical behavior after promotion. It verifies breadth of basic operation rather than exhaustive correctness.
Rollback: Reactivating a previous compatible release when evidence crosses a stop threshold. It should use a known artifact rather than rebuilding during an incident.

How to use a term during diagnosis

Name the observed symptom without assigning a cause.
Select the entity whose invariant is visibly wrong.
Identify its owner and adjacent dependencies.
Collect the evidence listed in the relevant guide.
Fix the earliest wrong boundary and verify the whole user path.

Sources and further reading

These references support the standards and factual claims in this guide. The decision frameworks and worked examples are original editorial synthesis.

Questions practitioners ask

Why define familiar terms such as cache or state?

Teams often use the same word for different layers. A shared definition identifies the owner, observable evidence, and boundary, reducing incorrect fixes.

Is the DOM the HTML source?

Not exactly. The browser parses source into a live document tree, and scripts can change that tree after parsing.

Is a release the same as a deployment?

A release is a versioned combination of build and configuration; deployment is the process that makes a release active in an environment.