The argument against page-wide grids

Donnie D'Amato's gridless.design makes a narrower point than its name suggests: the case is not against display: grid;, but against treating a single overall page grid as a mandatory framework. In his framing, digital designers still reach for the grid while experienced layout engineers have already moved past it.

Brad Frost, who sees far more projects than most, landed on the same tension between comps and implementation:

One of the most frequent, confusing conversations w/ designers is "No, the pink lines that overlay design comps aren't all that helpful for how things actually work in the browser."

[…] throw your transparent pink 12-column grids in the trash can.

Brad Frost, "Link post to gridless.desgn"

Old spirit, newer tooling

D'Amato treats the position as a continuation of responsive design, and that reading holds up — with the caveat that browsers have changed considerably since the term was coined, which may justify a new label. "Content-driven design," one of D'Amato's headings, captures it well.

Michelle Barker frames the same gap between available CSS and entrenched process:

CSS layout features like flexbox and Grid enable us to build more flexible layouts that prioritise content. We talk about intrinsic and extrinsic sizing in CSS — sizing based on both content and context. The promised container queries specification will put even more power in the hands of developers. But it feels to me like the design process is still stuck in the past.

Michelle Barker, "Is it Time to Ditch the Design Grid?"

Breakpoints as a last resort

Once container queries arrive in earnest, the page-level layout becomes an endangered pattern. D'Amato's guidance is to rule out other options before writing a viewport breakpoint. Breakpoints remain acceptable where a component is genuinely tied to page size — headers, modals and similar — but components nested deep in the page should not rely on them to determine layout.