feat(docs): Docs home and nav refresh with new designs#14178
feat(docs): Docs home and nav refresh with new designs#14178
Conversation
…s release automation files with latest from master
…ions from master to resolve conflicts and navigation issues
…les in nested sentry location
…uct section on home
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Bundle ReportChanges will increase total bundle size by 59.46kB (0.28%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
Files in
Files in
Files in
App Routes Affected:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
Files in
Files in
Files in
Files in
App Routes Affected:
|
|
|
||
| .search { | ||
| --sgs-bg-color: var(--gray-2); | ||
| --sgs-bg-color: #ffffff; |
There was a problem hiding this comment.
Dark mode search hover shows white background
Medium Severity
The --sgs-bg-color variable is hardcoded to #ffffff and never overridden for dark mode. The .sgs-offsite .sgs-hit-item > a:hover rule uses background-color: var(--sgs-bg-color), so hovering over offsite search results in dark mode renders a jarring white background. Previously this variable was var(--gray-2), which correctly resolved to a dark color in dark mode. The new dark mode override on .sgs-search-results only changes background-color directly — it doesn't update the CSS custom property.
There was a problem hiding this comment.
This is for ask AI. It's a production bug too. Seeing if I can fix it.
When clicking 'Platforms' in breadcrumbs, clear stored platform from localStorage so the SDK selector resets to default state. Co-Authored-By: Claude <noreply@anthropic.com>
…sentry/sentry-docs into docs-home-and-nav-refresh-v1
Clear 'active-platform' from localStorage before navigating to /platforms/ so the SDK selector doesn't auto-redirect to the previously selected SDK. Co-Authored-By: Claude <noreply@anthropic.com>
- Added Changelog and Sandbox external links to footer - Reorganized footer into two rows on desktop - Left-aligned stacked links on mobile Co-Authored-By: Claude <noreply@anthropic.com>
- Remove hover:scale-105 animation from SDK tiles - Add 1px more margin below icon for better text spacing Co-Authored-By: Claude <noreply@anthropic.com>
- Refactor Breadcrumbs to accept serializable items array instead of DocNode - Add buildBreadcrumbs helper in separate utils file for server components - Add platform-redirect handler to sidebarNavigation Co-Authored-By: Claude <noreply@anthropic.com>
- Change MobileSidebarNav breakpoint from lg-xl to md (768px) to match top nav - Fix mobile sidebar scroll by correcting height calc and adding min-height: 0 - Remove duplicate dropdown nav in MobileSidebarNav, use simple links instead - Add hamburger menu to home page with mobile navigation overlay - Show X icon when menu is open on all pages for consistency Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 5 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
- Delete unused TopNav.tsx server component - Remove unused useHomeSearchVisible export from homeSearchVisibility.tsx - Create shared navigationData.ts for nav sections used across components - Update TopNavClient, header, MobileSidebarNav, mobileMenu to use shared data - Consolidate duplicate CLI sidebar code into concepts handler Co-Authored-By: Claude <noreply@anthropic.com>
…More dropdown - Swap search bar and top nav so nav is anchored next to Docs logo - Reduce padding between logo and nav menu - Fix mobile Ask AI/theme toggle right-anchoring - Change nav labels to title case (SDKs, Product, Guides, Concepts, API) - Combine Admin and Security sections into new 'More' dropdown - Update sidebar to show all 'More' sections together Co-Authored-By: Claude <noreply@anthropic.com>
- Fix useState initializer reading localStorage during SSR in platformSelector - Restore lazy-loading for Search component using next/dynamic - Reduces initial bundle size by deferring Algolia/search JS loading Co-Authored-By: Claude <noreply@anthropic.com>
| import {NavLink} from './navlink'; | ||
| import {MagicIcon} from './cutomIcons/magic'; | ||
| import {useHomeSearchVisibility} from './homeSearchVisibility'; | ||
| import {mainSections} from './navigationData'; |
There was a problem hiding this comment.
Bug: The Search component is now imported directly, removing the previous next/dynamic lazy-loading. This will increase the initial JavaScript bundle size on all pages.
Severity: MEDIUM
Suggested Fix
Re-introduce lazy loading for the Search component by wrapping its import with next/dynamic. Set ssr: false in the dynamic import options, as was done in the previous implementation, to prevent it from being included in the server-side render.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: src/components/header.tsx#L17
Potential issue: The `Search` component is now imported directly in `header.tsx` and
`home.tsx`, removing the previous lazy-loading implementation that used `next/dynamic`.
This component includes heavy dependencies like Algolia and
`@sentry-internal/global-search`. The removal of lazy-loading means this JavaScript will
be included in the initial bundle for every page, increasing its size. This is a
performance regression of a previously fixed issue (DOCS-8BT) and will negatively impact
page load times, particularly Time to Interactive (TTI) and First Contentful Paint
(FCP).


DESCRIBE YOUR PR
This is a home page refresh and top navigation add to the docs site.
most used SDKsto top, add search barPreview: https://sentry-docs-git-docs-home-and-nav-refresh-v1.sentry.dev/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: