One Column, Full Measure
With both rails gone the article takes the full container width. This is the layout for pages where nothing should compete with the content: a long-form article, a legal page, a single detailed case study. Anything with one message deserves the whole page.
Full width doesn't mean full-width paragraphs — Apex's body copy is already capped by a comfortable line length via the container's max-width, so long-form text stays readable without an extra column doing the work.
Mixing Layouts Across a Site
Mixing layouts across a site is the point of the set: a full-width page like this one, articles with a right rail, documentation with a left one — all sharing the same header, off-canvas menu, and footer, so navigation feels seamless while each page gets the arrangement its content wants.
- No
.col-md-*split — one<section>, full container width - The natural default when no rail earns its keep
- Same header, off-canvas menu, and footer as every layout
- Compare with left-sidebar.html and right-sidebar.html
- When in doubt, start here and add a rail only when needed