Fix content column width and alignment on API reference pages - #3359
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
internal
pwizla
added
pr: chore
and removed
pr: updated content
Collaborator
Author
|
LGTM, the mode selector issues seem to be fixed now! |
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.
This PR makes API reference pages use the exact same content column as every other doc page. They previously forced the article to full width and re-centered each kind of child with per-child, per-width special cases that had drifted apart, so content ended up at a different width and position than on regular pages, the view-mode switcher sat ~52px left of the page title, and the width even differed between API pages. Content is now identical everywhere at each content width (narrow/wide/max), while endpoint blocks keep their two-column layout at wide/max.