feat: redesign blog search with real-time suggestions and tags filtering

[mrdeyroy]

Description

This PR completely redesigns the blog search experience to make it highly interactive and user-friendly. The motivation behind this change is to eliminate the friction of manual search submissions by providing real-time, grouped search suggestions (categorized into articles, tutorials, and tags) directly within a dynamic dropdown. It also modernizes the UI to match standard layout aesthetics, moving the search functionality seamlessly into the hero section.

Fixes #1637

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

• New BlogSearch Component: Built a debounced (300ms) live search input that groups dynamic results into Articles, Tutorials, and Tags.
• Hashtag Search Implementation: Added support for searching exclusively by tag/category by prefixing the search query with # (e.g. #netflix).
• Keyboard Accessibility: Handled ArrowUp, ArrowDown, Enter, and Escape for seamless navigation within the dropdown search results.
• Layout Improvements: Integrated the new component securely in the Hero section and fixed underlying z-index stacking contexts to prevent clipping over the "Explore Articles" container.
• Code Cleanup: Removed all old unused form search logic and obsolete .blog-search-* CSS from index.tsx and blogs-new.css.

Dependencies

• List any new dependencies or tools required for this change.
  • No new NPM packages were added. (Utilized existing @docusaurus/router for history pushes).
• Mention any version updates or configurations that need to be considered.
  • No version updates necessary.

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.

---

Screen Shots:

BEFORE:

AFTER:

Keyword Suggestions:

TAG Filter:

[vercel]

@mrdeyroy 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 #1637:

• Labels: level 1, recode, Enhacement, high priority, gssoc:approved
• Milestone: None

[mrdeyroy]

@sanjay-kv I hope it met your requirements. Please check if any changes needed!