refactor(docs): extract theme configuration into separate file

[gene9831]

and update vitepress config

Summary by CodeRabbit

• Refactor
  • Documentation theme configuration reorganized into a modular structure with improved navigation and sidebar organization. Configuration now spans dedicated sections for guide, components, tools, and examples.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR extracts VitePress theme configuration from the main config file into a dedicated module. A new themeConfig.ts file consolidates navigation and sidebar definitions for documentation sections (guide, components, tools, examples), and the main config now imports and spreads this configuration instead of defining it inline.

Changes

Cohort / File(s)	Summary
Configuration Extraction docs/.vitepress/config.mts	Added import of themeConfig from ./themeConfig; replaced inline theme configuration with spread operator applying the imported config object.
New Theme Configuration Module docs/.vitepress/themeConfig.ts	New file defining shared sidebar structure and navigation/sidebar mappings for multiple documentation sections (/guide/, /components/, /tools/, /examples/); exports themeConfig object.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Review the new themeConfig.ts for correct sidebar structure and navigation hierarchy
• Verify the import and spread operation in config.mts correctly applies the theme configuration
• Ensure all sidebar sections and navigation items are preserved and properly organized

Poem

🐰 Hop hop, configs take flight!
From scattered to neat, organized right.
Files find their home, structure takes shape,
Theme configuration: a well-crafted escape! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 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: extracting VitePress theme configuration from an inline object into a separate file (themeConfig.ts).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/.vitepress/themeConfig.ts (1)

1-2: Consider adding explicit type annotations.

For better IDE support and maintainability, consider adding VitePress type imports. This helps catch configuration errors at compile time.

+import type { DefaultTheme } from 'vitepress'
+
 // 定义共享的侧边栏配置
-const sharedSidebarItems = [
+const sharedSidebarItems: DefaultTheme.SidebarItem[] = [

And for the exports:

export const themeConfig: { nav: DefaultTheme.NavItem[]; sidebar: DefaultTheme.Sidebar } = { nav, sidebar }

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b775495 and 678d099.

📒 Files selected for processing (2)

• docs/.vitepress/config.mts (2 hunks)
• docs/.vitepress/themeConfig.ts (1 hunks)

🔇 Additional comments (2)

docs/.vitepress/themeConfig.ts (1)

1-61: Clean extraction of theme configuration.

The refactoring effectively separates concerns by moving navigation and sidebar configuration to a dedicated module. The use of sharedSidebarItems to avoid duplication across multiple routes is a good pattern.

docs/.vitepress/config.mts (1)

6-6: LGTM!

The import and spread integration are correctly implemented. The themeConfig is properly imported and spread into the VitePress theme configuration, maintaining the existing structure while delegating nav/sidebar definitions to the extracted module.

Also applies to: 67-67