Mobile-First Design
beginnerDefinition
A way of designing a website where you start by making it work beautifully on a small phone screen, and only then add the extra touches that make sense on bigger screens. Starting small forces you to decide what really matters and cut everything else.
In the wild
A team designs a recipe site by first laying out the perfect phone version: one column, big tappable buttons, no clutter. Once that's solid, they widen the layout for tablets and add a sidebar for desktops. The phone version was never an afterthought.
More from Frontend & Responsive Design
Accessibility (a11y)
Building websites and apps so that everyone can use them: including people who can't see well, can't use a mouse, are color-blind, or rely on a screen reader to read pages aloud. Accessibility is partly thoughtful design and partly small technical details done correctly.
ARIA (Accessible Rich Internet Applications)
A set of small labels you can add to webpage elements to tell screen readers and other assistive tools what each piece of the page is and what it's doing. ARIA is useful when the standard tags can't fully explain a custom widget on their own.
Box Model
The mental picture of how every element on a webpage is laid out. Each element is a rectangle made of four nested layers: the actual content in the middle, padding around it (the inner cushion), then a border, then margin (the outer breathing room before the next element starts).
Breakpoint
A particular screen width at which a webpage changes its layout to suit the new size. Below the breakpoint the page might show a single column for phones; above it, the same content might rearrange into a multi-column layout for tablets or desktops.
CSS Grid
A way of arranging things on a webpage into neat rows and columns at the same time: like a spreadsheet you can place items into. It's the right tool for page layouts, photo galleries, and anything that needs to line up in a tidy grid.
CSS Specificity
The way a webpage decides which style wins when several styling rules try to apply to the same element. The more precise a rule is, naming a particular item by ID rather than a whole group, the higher its priority. It's why a designer's careful tweak sometimes loses to an older, more specific rule they forgot existed.