Enhanced the UI for community page

[Richajaishwal0]

Description

Enhanced the community page with a modern, interactive design featuring a scrollable layout with table of contents navigation, comprehensive dark theme support, and improved user experience. The page now provides multiple ways for users to contribute to RecodeHive with clear sections for Code, Design, Documentation, Community engagement, and Getting Started guidance.

This enhancement transforms the basic community page into a professional, engaging interface that matches the overall RecodeHive design system and provides seamless navigation between contribution types.

Fixes #261

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

• Complete page redesign: Transformed from basic markdown to interactive TSX component with modern styling
• Scrollable layout: Implemented vertical scrolling with all contribution sections visible
• Table of Contents sidebar: Added sticky navigation sidebar with auto-scroll tracking and smooth navigation
• Enhanced Thank You section: Redesigned with colorful gradients, animated icons, feature cards, and glass morphism effects
• Comprehensive dark theme support: Full dark mode compatibility.
• Responsive design: Optimized for desktop, tablet, and mobile with adaptive layouts
• Interactive elements: Added hover effects, smooth animations, and professional styling
• Accessibility improvements: Enhanced contrast ratios and keyboard navigation support

Dependencies

• Framer Motion: Already included in project for animations and transitions
• React hooks: useState and useEffect for scroll tracking functionality
• CSS custom properties: Enhanced theming system for consistent styling
• No new external dependencies required - leverages existing project infrastructure.

Checklist

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

Dark theme:

[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! 😊

[vercel]

@Richajaishwal0 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
recode-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 6, 2025 1:02pm

[sanjay-kv]

Hi @Richajaishwal0 One suggestion for you is always run "npm run build" before push.
Do pull before push.