Full-bleed elements inside a narrow, centered reading column usually rely on a well-known workaround: relative positioning on the left plus a negative viewport-relative left margin. It works, but it is fussy — it wants the container to be centered and it wants hidden overflow on the body. On the plus side, the rest of the container's content is unaffected.

A second approach that keeps coming up in write-ups is CSS grid. Tyler's "Breaking Out with CSS Grid Layout," Rachel Andrew's reply explaining it, her later piece on editorial design patterns with named columns, Selen Gora's container breakout demo, and Bryan Robinson's article on full-width stripes with subgrid all take this route.

The shared assumption

Every one of those techniques assumes an edge-to-edge grid already exists — essentially that the page itself is a grid, or that some full-browser-width parent is. Posts tend to express this as a class, but the underlying premise is that grid runs the entire width of the viewport.

That premise deserves a second look, because a site-wide grid brings some awkward obligations:

  • Headers and footers are typically full-width already. Under a grid, you have to place them explicitly and stretch them across the right column span, then keep that span correct whenever the column setup changes — rather than letting a plain block-level sit at the top of the page. A grid can remain in the middle, with ordinary block elements above and below it.
  • Article content needs to be placed, e.g. article > * { grid-columns: 2 / 3; }, purely so that the occasional element can span further and stretch. When around 95% of content stays in one centered column, putting that content in a parent that owns the layout is more robust than having each element place itself on the grid to create the appearance of a shared parent.

A caveat about the body

The one rule worth stating plainly: avoid display: grid; directly on the body. Browser extensions can inject nodes into the body, and those nodes then become grid items and can disturb the layout — something that has been observed in practice. The safer pattern is to scope the layout to a child selector, much as React advice warns against binding to the whole body.