doc: explore denser sidebar sponsors layouts - #1489
Conversation
The sidebar sponsors aside only fits three card-style slots before pushing content below the fold. Five denser layout candidates on the internal design-system page help pick a replacement, previewed with extra sponsors of various logo styles and aspect ratios.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
franky47
added
documentation
franky47
changed the title
Review flight suggested passing logos as components instead of render-prop arrows, deduplicating new-tab link attributes, and dropping per-variant comments that duplicated the rendered captions.
1 participant
The sidebar sponsors section is getting crowded: three card-style slots already push the docs table of contents around, and there is no room for the sponsors we would like to add next.
This adds a Sidebar sponsors section to the internal design-system page with five denser layout candidates, rendered at sidebar width next to the current layout for comparison. Extra slots are filled with sponsors from the landing page, picked for their variety of logo styles and aspect ratios (wide wordmark, icon lockup, circular and square avatars).
The candidates:
One finding from the dark-mode pass: logos drawn on dark circles (Sentry, Upstash) nearly vanish on the dark background once grayscaled, so whichever layout wins may need per-sponsor light variants.
Along the way,
sponsors.tsxlost some duplication: the Next.js Weekly wordmark and shadcn/studio icon are now standalone components, andSPONSORSis exported so the lab can reuse the landing-page data.