make badges circular and fix hover behavior

[steam-bell-92]

Description

Improved the visual appearance and hover behavior of contributor badges in the leaderboard component. Badges are now circular and only scale when directly hovered, preventing unintended animations when hovering over the parent container.

Fixes #1203

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

• Changed contributor badge icons from rounded squares to perfect circles (border-radius: 50%)
• Removed padding from badge icons for a cleaner, more compact appearance
• Added CSS rule to prevent badge icons from scaling/showing shadow when hovering the parent badges container

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors.
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

@steam-bell-92 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

✅ Synchronized metadata from Issue #1203:

• Labels: level 1, recode, wcos
• Milestone: recode:launch 3.0

[Adez017]

Hi @steam-bell-92 , can you share a video with the changes , it would help in better review .

[steam-bell-92]

I am unable to get a video as I am encountering

Error: GitHub token not found. Please set customFields.gitToken in docusaurus.config.js.

Which I am unable to solve from my side. But I can share ss which I had earlier

[Adez017]

@steam-bell-92 , could you reduce the border margin as the white border look a bit bigger

[steam-bell-92]

@steam-bell-92 , could you reduce the border margin as the white border look a bit bigger

Noted

[steam-bell-92]

Will no margin help or need some margin

[Adez017]

Will no margin help or need some margin

i would suggest no margin . lets take the call from @iitzIrFan

[github-actions]

✅ Synchronized metadata from Issue #1203:

• Labels: level 1, recode, wcos
• Milestone: recode:launch 3.0

[steam-bell-92]

For now made them half but if no margins is expected then will make similar changes after confirmation

[iitzIrFan]

let's go with no margin as they are badges and are looking a bit off on margin @steam-bell-92

[github-actions]

✅ Synchronized metadata from Issue #1203:

• Labels: level 1, recode, wcos
• Milestone: recode:launch 3.0

[steam-bell-92]

@Adez017 @iitzIrFan

[Adez017]

hi @steam-bell-92 , lets wait for @sanjay-kv to trigger the deployment.