Bound and center content app-wide (--content-max)#38
Draft
CST-100 wants to merge 1 commit into
Draft
Conversation
Content width becomes a global budget: .main is bounded to --content-max and centered, so wide viewports split slack symmetrically instead of pooling it right of left-anchored pages (issue tickets being the worst case). Chrome stays full-bleed; the breadcrumb bar aligns its text to the centered content edge. ok.panel(max_width=...) panels now self-center, and the survey pass fixed the stragglers that bounded by hand without centering (settings index, project wizard, docs, styleguide). The exec-tabs strip is content, not chrome — comment updated to match its behavior under the bounded main. Also converts the scrap modal on the OPAL detail page to a real fixed overlay: it referenced .modal-overlay/.modal-content classes that exist nowhere, so it rendered in document flow at the bottom of the page — pre-existing, surfaced by the width survey. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Split out of #36 to review independently.
Content width becomes a global budget:
.mainis bounded to--content-max: 1400pxand centered, so wide viewports split slack symmetrically instead of pooling it to the right of left-anchored pages (issue tickets were the worst case). Chrome stays full-bleed; the breadcrumb bar pads its text to the centered content edge so crumbs and content read as one column.ok.panel(max_width=...)panels now self-center, and a 10-agent template survey caught the four pages that bounded by hand without centering (settings index, project wizard, docs, styleguide) — they'd otherwise jump ~90px when navigating between siblings.Also fixes a pre-existing bug the survey surfaced: the scrap modal on the OPAL detail page referenced
.modal-overlay/.modal-contentclasses that exist nowhere in the CSS, so it rendered in document flow at the bottom of the page instead of as an overlay. Converted to the fixed-overlay pattern its sibling modals in the same file already use.Note: on the parts redesign branch (#36) the part page's
.part-layoutcenters its column tracks; that composes cleanly with this change (tracks center within the bounded main). Neither PR depends on the other to merge.🤖 Generated with Claude Code