journal: archive wide-viewport whitespace investigation (resolved by #76)#77
Merged
Merged
Conversation
#76 The 2026-05-08 social-launch screenshot batch surfaced that the homepage showed ~35% horizontal whitespace at 1280-wide viewports because the site had only one media query (max-width: 640px). The investigation sat in a feature worktree alongside the launch assets and was never committed at the time. PR #76 has now resolved it: the new `min-width: 1100px` breakpoint widens `--max-w` from 52rem to 64rem, applying option 1 from the journal's option list. The two-column layout and decorative-frame options were rejected because they conflict with rules/design-intent.md §5 — wide viewports widen content, not whitespace, and not chrome. Also: - ROADMAP gets three matching [x] entries for PR #74/#75/#76 in Now - .gitignore adds assets/social/ — launch screenshots are local-only promotional artifacts, not committed alongside the source Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Archives a 2026-05-08 investigation that had been sitting uncommitted in a feature worktree until today, and closes the loop with the fix that just shipped.
journal/2026-05-08-wide-viewport-whitespace.md records:
max-width: 640px) and a fixed--max-w: 52rem@media (min-width: 1100px)widening--max-wto64rem. The two alternative options (2-col layout, decorative frame) were rejected because they conflict withrules/design-intent.md§5 (wide viewports widen content, not whitespace or chrome)ROADMAP.md gains three matching
[x]rows in Now for #74 / #75 / #76..gitignore adds
assets/social/— launch screenshots are local promotional artifacts. The first batch (May 8) is staying on disk but won't be committed.Why this matters
The journal entry is exactly the "failures captured for agent self-evolution" use case in CLAUDE.md. Without committing it, the institutional memory of why PR #76 added that specific breakpoint at 1100px (and not, say, 1280px or 1440px) would have been lost. This PR makes the chain
1280px screenshot reveals issue → root cause → option list → chosen fix → rule §5discoverable from a single file.Tested
Lint-only / docs-only changes. No build impact.