Navbar UI improvements

[Abhishek-Sonje]

Summary

Updated the navbar design to better align with the site’s dark, cyber-inspired theme.

Changes Made

Replaced placeholder circle icon with the official TechXNinjas logo.

Added neon green/cyan accents for active icons.

Implemented hover glow and slight scale-up animation for sidebar icons.

Restyled the search bar with a dark theme and glowing border.

Improved visual alignment of logo and brand text.

Purpose

These changes improve brand consistency, enhance UI aesthetics, and make the navbar feel more integrated with the overall site design.

Screenshots
Before:

After:

Issue Reference
Closes #177

Next Steps

Please review and let me know if any additional tweaks are needed.
If everything looks good, I can proceed with merging.

[vercel]

@Abhishek-Sonje is attempting to deploy a commit to the TechXNinjas' projects Team on Vercel.

A member of the Team first needs to authorize it.

[anshkumar2311]

Hei @Abhishek-Sonje I am also asign to do the same issue. Your navbar is good but I have a question where you get this logo is their official logo or you have added by your side ??

[Abhishek-Sonje]

Hei @Abhishek-Sonje I am also asign to do the same issue. Your navbar is good but I have a question where you get this logo is their official logo or you have added by your side ??

There is separate jpg file for logo in repo

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
18449075	Triggered	JSON Web Token	0e108cf	components/layout/SearchHeader.tsx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
techxninjas-client	Ready	Preview	Comment	Aug 16, 2025 9:22am