feat(navbar): redesigned navbar using TailwindCSS

[isha54ry]

Describe the changes that are made

• Added smooth hover transitions on navbar items for better interactivity.
• Redesigned the navbar using TailwindCSS to improve its usability and visual appeal.
• Applied a consistent dark theme with modern styling across layout and content.
• Preserved original functionality and structure while enhancing responsiveness and hover effects.

Links & References

Fixes: #2769

🔗 Related PRs

• NA

🐞 Related Issues

• NA

📄 Related Documents

• NA

What type of PR is this? (check all applicable)

• 📦 Chore
• 🍕 Feature
• 🐞 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🔁 CI
• ⏩ Revert

Added e2e test pipeline?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added comments for hard-to-understand areas?

• [x]👍 yes
• 🙅 no, because the code is self-explanatory

Added to documentation?

• 📜 README.md
• 📓 Wiki
• 🙅 no documentation needed

Are there any sample code or steps to test the changes?

• 👍 yes, mentioned below

To test:

• Run yarn start in the root directory.
• View the updated dark-themed navbar on the top of the homepage.
• Hover over navbar items to see interactive effects.

Self Review done?

• ✅ yes
• ❌ no, because I need help

Any relevant screenshots, recordings or logs?

Screen.Recording.2025-06-19.041122.mp4

🧠 Semantics for PR Title & Branch Name

Please ensure your PR title and branch name follow the Keploy semantics:

📌 PR Semantics Guide
📌 Branch Semantics Guide

Examples:

• PR Title: feat(navbar): redesigned navbar using TailwindCSS
• Branch Name: feat/modified-navbar

---

Additional checklist:

• Have you read the Contributing Guidelines on issues?
• Have you followed the PR Semantics guide for naming this PR?
• Have you followed the Branch Semantics guide for naming your branch?

[github-actions]

Thank you and congratulations 🎉 for opening your very first pull request in keploy

[pratik-mahalle]

Hey @isha54ry , Thank you for raising the pr, Our team will review the pr soon before that please make sure to sign the DCO.