.wrap is a three-column grid: a flexible track on each side and a content column in the middle. Every child is placed in the middle column, so text stays at a comfortable reading width.
On this page, the tinted area is the wrapper and each dashed box is one of its children. There are two ways to get wider than the content column depending on the situation: is one element wide, or is the whole section wide?
.wrap_content-flushThis wrapper is a plain .wrap, the usual setup for an article or a docs page. Almost everything here is text that should stay in the reading column.
Sometimes one element needs the full viewport: a hero image, a banner, a colored call-out. Put .wrap_content-flush on that one child and leave its siblings alone.
This child has .wrap_content-flush. It spans all three grid columns, side tracks included, so its background reaches both edges of the viewport. Its content still gets the wrapper’s padding on small and medium screens.
The next sibling is back in the content column. The modifier changed one child, not the wrapper, so you can break out as many times as the page needs and return to the reading width after each one.
.wrap-flushThis wrapper has .wrap-flush. The preset sets the content column to 100%, so the side tracks collapse to nothing and every child spans the viewport, with the wrapper’s padding applied to each of them.
Use it when the whole section is wide content: a gallery, a row of cards, a dashboard, a large table. If you find yourself adding .wrap_content-flush to every child, put .wrap-flush on the wrapper instead.
On large screens a plain .wrap drops its padding (--wrap-lg-spacing) because the side tracks supply the margin. A .wrap-flush section has no side tracks, so it keeps a gutter there instead (--wrap-flush-lg-spacing). A .wrap_content-flush child does not, so a flush image can still touch both edges.