Studio Code: widen the default content width and use wide layouts for grids - #4779
Merged
Conversation
…widths Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Collaborator
📊 Performance Test ResultsComparing bcc1b89 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
1 task
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
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.
Related issues
How AI was used in this PR
Claude Code investigated where the agent's content width comes from, drafted the skill wording and the default change, and ran six FamilyFarm site builds (DeepSeek V4 Flash) to check the outcome. The author reviewed the wording and picked the width ranges and the new defaults.
Proposed Changes
Sites built by Studio Code tended to feel narrow. Two things caused it:
scaffold_themeset a 720px content width, and the agent was told to "retune" it without any guidance on what a suitable value looks like, so it usually left it alone.block-contentskill only described full-bleed and constrained patterns, and never mentionedalign: "wide". Card grids, feature rows, and galleries were squeezed into the reading column (about 220px per column in a three-column row) even thoughwideSizewas declared.This PR makes three small changes:
block-contentskill gains a "full-bleed section, wide inner content" pattern: columns, grids, and galleries inside a section goalign: "wide"so they use the wide width, and the reading column is reserved for text-only blocks.visual-designskill tells the agent how to tune the widths per site type: keep the defaults for marketing pages, narrow to 700–860px for editorial reading columns, and keepwideSizeat 1200–1400px.User impact: new sites get full-width card rows and a wider text column out of the box, and the agent varies the width per site type instead of always shipping the same 720px column.
Testing Instructions
npm run cli:build, then runstudio codewith a one-page site prompt such as:Build a farm one page site, known for its animals visits and its local products. The farm is called "FamilyFarm". Use elegant colors and design.theme.json:settings.layout.contentSizeshould be around 1000px (not 720px) andwideSize1200–1400px.alignwideclass and span the wide width rather than the reading column.align: "wide"for their grids and chose content widths between 720px and 1080px before the default change and 920px to 1080px after it.Pre-merge Checklist
🤖 Generated with Claude Code