Content first
Responsive design means a page adapts to the space and device it appears on. MDN describes it as an approach that makes web pages render well on a variety of devices and window sizes. The practical start is simple: begin with the smallest layout, which forces you to prioritize, and enhance for larger screens.
Breakpoints that follow content
Rather than targeting specific phones, resize the browser and watch for where the design starts to look wrong. Add a breakpoint there. This produces fewer, more meaningful breakpoints.
- Use relative units such as rem, em, and percentages.
- Let grids use flexible tracks, for example repeat(auto-fit, minmax(16rem, 1fr)).
- Use fluid type with clamp() so headings scale smoothly.
- Set max widths for text so lines stay readable.
Components that adapt themselves
Container queries let a component respond to the size of its container, not the whole window. A card can switch between a stacked and a side-by-side layout depending on the space it is given. This makes components reusable across contexts without special cases.
Responsive is more than width
| Factor | Consider |
|---|---|
| Input | Touch, mouse, and keyboard, with enough size for fingers |
| Network | Slow connections and image sizes |
| Preferences | Dark mode, reduced motion, larger text |
| Orientation | Landscape on phones and tablets |
| Content | Long names, translations, and user-generated text |
Test beyond the browser resize
Open the site on real phones and tablets. Try it with the keyboard, with zoom at 200 percent, and on a throttled connection. A layout that only works at a few widths is not responsive, just lucky.



