Fix API reference content/code-rail collision#327
Open
bcrowther1 wants to merge 2 commits into
Open
Conversation
Our global 820px content-centering rule ignored the sticky request/response code rail on OpenAPI endpoint pages, so the prose slid under it on narrower viewports. Scope the centering off for /api-reference/endpoint/ pages (all locales) and let Mintlify's native two-column layout reserve the rail. Co-authored-by: Cursor <cursoragent@cursor.com>
The prior fix widened the prose to full width on large screens. Instead keep the same 820px column and, on /api-reference/endpoint/ pages, center it within its own flex track (not the viewport) so it never crosses into the sticky code rail. Verified no overlap from 1440px through 1920px, including the ~1650-1765px band where the collision occurred. Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
#content-arearule uses viewport-based centering (50vw), which above 1650px pushes the 820px column rightward into the rail's flex track./api-reference/endpoint/pages center it within its own flex track instead of the viewport, so it can never cross into the rail. Scoped by path (covers all locales); plain API pages (Introduction/Rate Limits/Error Codes) and all normal docs pages are unaffected.Test plan
/api-reference/endpoint/image/generate,/api-reference/endpoint/chat/completions)./es/api-reference/endpoint/image/generate).Made with Cursor