fix: dark mode support for Sponsors and Blogs pages

[abhishekkalme]

Description

This PR enhances the dark/light theme compatibility for the Our Sponsors and Blogs pages in the project. It applies contextual color support using CSS variables and useColorMode() hook from Docusaurus. The aim is to provide a seamless viewing experience across themes without compromising UI/UX consistency..

Fixes #218 (🐞[Bug]: Dark Mode Styling Issues on /our-sponsors and /blogs Pages)

Type of Change

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

Changes Made

• Refactored OurSponsors and Blogs pages to use CSS custom properties (:root and [data-theme='dark']) for dynamic color support.
• Removed hardcoded tailwind dark: classes and replaced them with reusable CSS class logic.
• Introduced or updated Sponsors.css and Blogs.css for theme styling.
• Ensured that text, background, buttons, and other UI elements adapt according to selected theme.
• Cleaned up unnecessary classNames for better readability

Dependencies

• No new dependencies added.
• Ensure Docusaurus theme provider is active () — already included by default in Docusaurus.

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

Our Sponsors Page	Blogs Page	Npm Run Build

✅ Ready for Review
Please let me know if any changes are needed. Looking forward to your feedback!
Thanks for the opportunity to contribute. 😊

[vercel]

@abhishekkalme 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	❌ Failed (Inspect)			Jul 29, 2025 0:19am

[sanjay-kv]

http://localhost:3000/docs/category/sql/
http://localhost:3000/docs/sql/intro-sql
http://localhost:3000/blog/ux-ui-design-job
http://localhost:3000/community
http://localhost:3000/broadcasts/
http://localhost:3000/podcasts/

Hi @abhishekkalme there is few more inconsistencies in he dark mode. can you help me to fix it.

[sanjay-kv]

Your Vercel build is failing with this error for many routes:

This means a component (likely your custom NavbarContent or similar) is using the useNavbarMobileSidebar React hook, but is not wrapped in the required context provider (). This breaks Docusaurus static site generation (SSG).

Hook useNavbarMobileSidebar is called outside the <NavbarMobileSidebarProvider>.

How to fix:

Check your custom Navbar code
If you have customized the Navbar (e.g., via src/theme/NavbarContent.js or src/theme/Navbar/index.js), make sure any usage of useNavbarMobileSidebar is inside the .

@abhishekkalme

So i reverted the changes