fix(docs): isolate sidebar nav styles

[jonathanperis]

Summary

• Replace the docs sidebar nav wrapper with div to avoid global nav styles breaking the side menu.
• Keep the shared docs/src/pages/docs/sidebar.config.ts structure used by sibling docs sites.

Verification

• bun run build

Summary by CodeRabbit

• Style
  • Minor markup adjustment to documentation sidebar navigation with no impact on appearance or functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

The sidebar navigation container in an Astro documentation page was changed from a semantic <nav> HTML element to a generic <div> element. The class name, styling, and nested structure remain unchanged.

Changes

Sidebar Navigation Container Markup

Layer / File(s)	Summary
Container Element docs/src/pages/docs/[...slug].astro	Sidebar navigation wrapper changed from <nav class="sidebar-nav-container"> to <div class="sidebar-nav-container">.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: replacing a <nav> element with a <div> to isolate sidebar navigation styles and prevent global nav styles from interfering.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/normalize-docs-structure

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/src/pages/docs/[...slug].astro (1)

96-118: ⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Reconsider removing semantic <nav> element—CSS specificity should handle global nav styles.

The sidebar navigation was changed from <nav> to <div> to prevent global nav styles from affecting the sidebar. However, the existing CSS selectors already have higher specificity: .docs-layout .sidebar-nav-container (class-based) overrides the global nav selector (element-based). The CSS conflict cited as justification does not appear to be real.

More importantly, replacing <nav> removes a semantic landmark that screen readers and assistive technologies rely on for page navigation. This degrades accessibility for users with disabilities.

Recommended fix: Revert to <nav class="sidebar-nav-container"> and rely on existing CSS specificity. The .docs-layout .sidebar-nav-container selector already prevents global nav styles from affecting the sidebar. If reverting is not an option, add ARIA attributes to restore semantic meaning:

<div class="sidebar-nav-container" role="navigation" aria-label="Documentation navigation">

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/src/pages/docs/`[...slug].astro around lines 96 - 118, The sidebar
navigation was converted from a semantic <nav> to a <div>, which removes an
important accessibility landmark; revert the wrapper element in the
SECTION_CATEGORIES rendering from a <div class="sidebar-nav-container"> back to
a semantic <nav class="sidebar-nav-container"> so screen readers regain the
navigation landmark (CSS specificity for .docs-layout .sidebar-nav-container
will continue to override global nav styles), and if reverting is impossible for
some reason, instead add role="navigation" and aria-label="Documentation
navigation" to the existing div to restore equivalent accessibility.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@docs/src/pages/docs/`[...slug].astro:
- Around line 96-118: The sidebar navigation was converted from a semantic <nav>
to a <div>, which removes an important accessibility landmark; revert the
wrapper element in the SECTION_CATEGORIES rendering from a <div
class="sidebar-nav-container"> back to a semantic <nav
class="sidebar-nav-container"> so screen readers regain the navigation landmark
(CSS specificity for .docs-layout .sidebar-nav-container will continue to
override global nav styles), and if reverting is impossible for some reason,
instead add role="navigation" and aria-label="Documentation navigation" to the
existing div to restore equivalent accessibility.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 39dea22f-5b24-4cc0-8086-5615ba5cb112

📥 Commits

Reviewing files that changed from the base of the PR and between 301cb70 and 48592e7.

📒 Files selected for processing (1)

• docs/src/pages/docs/[...slug].astro