Version Selector Dropdown UX Improvement

🧭 Problem Statement

I've identified a UX issue where the version selector dropdown (4.x / 3.x / 2.x) appears globally in the navigation bar — including on the homepage.
This creates confusion because:

• Homepage Context: The homepage serves as a version-agnostic introduction to Socket.IO.
• Immediate Redirect: Clicking any version instantly navigates away from the homepage to documentation.
• Context Mismatch: Version selection is only relevant within documentation pages.

💡 Proposed Solution

Conditionally render the version selector dropdown only when users are browsing documentation pages (/docs/ routes), keeping the homepage clean and focused.

⚙️ Implementation Ready ✅

This fix has already been implemented locally and is ready for a pull request.

Highlights:

• Uses Docusaurus routing to detect when the user is on documentation pages.
• Maintains all existing version functionality within docs.
• Provides a cleaner navigation architecture.
• Non-breaking and minimal in scope.

🌟 Why This Improvement Matters

• Better UX: Reduces cognitive load on the homepage.
• Cleaner Architecture: Keeps UI elements where they belong.
• Intuitive Navigation: Prevents confusing redirects from the homepage.

If this improvement aligns with the project’s vision, I’d be grateful for the opportunity to contribute this fix.
Please let me know if I can proceed with submitting the pull request.

Start at the global navigation component that renders the version selector and use Docusaurus routing to identify documentation pages. Verify that the selector remains available on /docs/ routes but is absent from the homepage, while version navigation within documentation continues to work.