fix: unify FAQ section color scheme and restore FAQs label

[vishalm342]

Description

This PR unifies the color scheme of the FAQ section to match the overall website design. It removes an unwanted blue line at the top of the FAQ section and restores the "FAQs" label with a consistent gradient color. These changes improve visual consistency and user experience.

Fixes #1032

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

• Updated FAQ section background to a dark-to-purple gradient for consistency.
• Removed the blue line at the top of the FAQ section.
• Restored and styled the "FAQs" label with a new gradient color.
• Ensured FAQ cards and text remain readable and visually consistent.

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.

[vercel]

@vishalm342 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 #1032:

• Labels: enhancement, level 1, recode, hacktoberfest-accepted
• Milestone: recode:launch 3.0

[vishalm342]

@sanjay-kv Hi this PR is from my fork. The Vercel deployment workflow is blocked because it requires authorization to access deployment secrets. Could someone with admin privileges please approve the pending workflow runs so the Vercel check can run? Thanks!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
recode-website	Ready	Preview	Comment	Oct 24, 2025 11:35am

[vishalm342]

@sanjay-kv if the task is completed from my side please merge the PR and love to contribute more.
Thanks!

[sanjay-kv]

@vishalm342 this is nice update .. loved it