fix: docs ui improvements and component improvements

[rohanchkrabrty]

Description

This PR fixes bugs in Docs

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor (no functional changes, no bug fixes just code improvements)
• Chore (changes to the build process or auxiliary tools and libraries such as documentation generation)
• Style (changes that do not affect the meaning of the code (white-space, formatting, etc))
• Test (adding missing tests or correcting existing tests)
• Improvement (Improvements to existing code)
• Other (please specify)

How Has This Been Tested?

Manual

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
apsara	Ready	Preview, Comment	Jan 7, 2026 7:29am

[ravisuhag]

@rohanchkrabrty why do we need hardcode navbar background ? Wouldn't this give wrong impression of default style of component?

[rohanchkrabrty]

@rohanchkrabrty why do we need hardcode navbar background ? Wouldn't this give wrong impression of default style of component?

@ravisuhag This is specific to the docs navbar, not the main navbar component. The transparent effect requires the color to be hardcoded instead of variables

[paanSinghCoder]

@p4suhag @rohanchkrabrty I think we should add some vertical gap between the hover in docs sidebar.

[paanSinghCoder]

@rohanchkrabrty The size input takes n values instead of just 1-6. A dropdown would make more sense here I think.