UI: Improve Community Page Visual Consistency and Alignment

[srushti-panara]

Description

This PR refines the Community page by improving spacing, alignment, visual consistency, and dark mode styling while preserving the overall structure and functionality of the page.

Fixes #1771

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

• Refined spacing between the main content area and the Table of Contents sidebar to improve layout balance.
• Improved alignment and spacing of section headers for a cleaner and more consistent appearance.
• Fixed alignment of icons and text in the resource links section to enhance readability.
• Refined active Table of Contents item styling by improving border-radius consistency and visual structure.
• Updated spacing and alignment across Community page components for a more polished user experience.
• Enhanced card shadows and visual hierarchy to better distinguish interactive elements.
• Improved dark mode styling by refining backgrounds, shadows, and contrast for better readability and consistency.
• Adjusted hover and active states to provide clearer visual feedback while maintaining the existing design language.

---

Before Screenshot

After Screenshot

---

Before Screenshot

After Screenshot

---

Before Screenshot

After Screenshot

---

Dependencies

• No new dependencies added.

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.

Note

The changes in this PR are limited to styling refinements within community.css and do not modify the page structure or functionality.

[vercel]

@srushti-panara 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 #1771:

• Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
• Milestone: recode:launch 3.0

[sanjay-kv]

can u do pull and push need, to resolve conflicts

[github-actions]

✅ Synchronized metadata from Issue #1771:

• Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
• Milestone: recode:launch 3.0

[github-actions]

✅ Synchronized metadata from Issue #1771:

• Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
• Milestone: recode:launch 3.0

[github-actions]

✅ Synchronized metadata from Issue #1771:

• Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
• Milestone: recode:launch 3.0

[srushti-panara]

Hi @sanjay-kv ,

I've pulled the latest changes from the upstream repository, resolved the merge conflict in community.css, and pushed the updated branch.

The PR is now up to date with the base branch and GitHub shows no merge conflicts. Please let me know if any further changes are required.

Thank you!

[Adez017]

lets trigger the CI @sanjay-kv

[github-actions]

✅ Synchronized metadata from Issue #1771:

• Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
• Milestone: recode:launch 3.0