progressive enhancement
Building a page that works everywhere first, then adding better features for browsers that support them.
In more detail
For example, cards use a simple flex column that works in every browser, and an @supports block upgrades them to subgrid where available. Nothing breaks for older browsers; they just get the simpler version.
Example
A server-rendered React form whose action is a Server Function can submit before its JavaScript loads.Related terms
- @supports — A CSS rule that applies styles only if the browser supports a given property, value or selector.
- fallback — A second choice used when the first is unavailable, such as a simpler layout for older browsers or a default value when a variable is missing.
- subgrid — A CSS Grid value that lets a nested grid use its parent grid's tracks instead of sizing its own, so content in separate cards lines up.
- form action — The action prop of a form, or formAction on a button, which in React can be a Server Action that receives the submitted FormData.
- hydration — The step where React in the browser attaches event handlers and state to HTML that was already rendered on the server.
- server-side rendering — Building a page’s HTML on the server for each request, so the browser can show content before any JavaScript runs.
- Server Functions — Async functions marked with "use server" that run on the server but can be called from client components, for example as a form action.
Taught in
- CSS Subgrid: Inheriting Track Sizing Across Nested Layouts — Frontend Architecture & Web Platform
- Server Actions: use server Directives & Mutations — Next.js 15 & Modern App Router Architecture
- useActionState: Async Action Handlers And Pending States — React 19 & Modern Component Architecture