Skip to content

Version Selector Dropdown UX Improvement #506

@Harsh3991

Description

@Harsh3991

🧭 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions