Fixed bugs for theme/footer and warnings related firebase

[Richajaishwal0]

Description

Fixed critical theme switching issues, Firebase console errors, and improved overall user experience. The website now has proper light/dark theme functionality with instant switching, clean button styling, and resolved Firebase API rate limiting errors.

Fixes #279
Key Issues Resolved:

• Theme toggle was not working smoothly (1-second delay)
• Buttons had inconsistent black/white boxes in light theme
• Firebase API errors flooding console due to rate limits
• Default theme not properly set to light mode
• Footer styling affected by theme changes

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)

Changes Made

Theme System Overhaul:

• Fixed default theme to properly load in light mode
• Fixed button styling inconsistencies across themes
• Protected footer from theme changes

Firebase Error Resolution:

• Fixed duplicate Firebase component loading
• Added proper error handling for GitHub API rate limits
• Implemented graceful fallback data for API failures
• Reduced console errors from 25+ to minimal warnings

UI/UX Improvements:

• Enhanced theme toggle with proper sun/moon icons
• Added hover effects and smooth animations
• Improved button contrast and styling consistency
• Ensured entire website follows theme properly

Dependencies

No new dependencies added. All fixes use existing:

• Docusaurus theme system
• Existing Firebase configuration
• Current CSS framework

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 screenshot in this PR
• This is already assigned Issue to me, not an unassigned issue
  Screenshot
  Footer for dark theme:

Firebase related issue solved:

[vercel]

@Richajaishwal0 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! 😊

[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 9, 2025 3:10pm

[sanjay-kv]

awesome