fix(page-content): align the masthead, prose, and pagination on one theme column - #2382
Merged
Merged
Conversation
…heme column #2380 swapped the prose section from `px-container` to `layout-boundary-inline`, but that utility only sets the inline gutter — the measure and the centering live in the `layout-column-*` utilities, whose max-width rule is nested behind `&:is(.layout-boundary, .layout-boundary-inline)`. The prose lost both and ran the full width of the content column, 193px left of the title it sits under. Finish the migration instead of reverting it. The three blocks of the article now read one COLUMN constant, and the masthead — still full bleed, so its rule stays the page's horizon — derives its inset from the same two tokens rather than a hand-written copy of `px-container`'s math, which drops the media query with it. `px-container` had no callers left, so it goes. Measured on the dev server: title, prose and pagination all land on 515 -> 1391 at 1920. Alignment holds across 11 container widths x both values of `--layout-boundary-inline`, covering both branches of the `max()`. The prose measure changes from 960px to 876px: no theme column reproduces 960 (`px-container` put the gutter inside its max-width, the theme columns put it outside), and `--layout-measure-content` is the token named for this.
marcus-souza-azion
merged commit Sep 21, 2026
71fac2d
into
release/new-azion-docs
6 of 8 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
#2380 swapped the prose section from
px-containertolayout-boundary-inline, but that utility only sets the inline gutter — the measure and the centering live in thelayout-column-*utilities, whose max-width rule is nested behind&:is(.layout-boundary, .layout-boundary-inline). The prose lost both and ran the full width of the content column, 193px left of the title it sits under.This one finishes the migration instead of reverting it. The three blocks of the article now read one COLUMN constant, and the masthead — still full bleed, so its rule stays the page's horizon — derives its inset from the same two tokens rather than a hand-written copy of
px-container's math, which drops the media query with it.px-containerhad no callers left, so it goes.Measured on the dev server: title, prose and pagination all land on 515 -> 1391 at
1920. Alignment holds across 11 container widths x both values of
--layout-boundary-inline, covering both branches of themax().The prose measure changes from 960px to 876px: no theme column reproduces 960 (
px-containerput the gutter inside its max-width, the theme columns put it outside), and--layout-measure-contentis the token named for this.Type of change
feat)fix) — typo, broken link, wrong informationdocs) — rewrite, expansion, upkeepi18n)refactor/chore) — reviewed by UXE, no content mixed inAuthor checklist
type(scope): summary(see GOVERNANCE.md §4)title,description,meta_tags,namespace,permalink,last_reviewedpt-brupdated in this PR or follow-upi18nissue created:pnpm build:local(build + frontmatter check) without errors