[FEATURE] Add Search Functionality for Subjects/Topics

[pushkarscripts]

Feature Description

Add a search functionality to help users quickly find subjects and topics across the platform.

The search should improve navigation and make it easier to access relevant content without manually browsing through semesters or subject lists.

Problem It Solves

Currently, users have to manually scroll through all available subjects and content sections to find what they are looking for. As more subjects and documentation get added, navigation becomes slower and less convenient.

A search feature would improve usability and accessibility, especially for users accessing the platform on mobile devices or looking for specific topics quickly.

Proposed Solution

Implement a lightweight search system that allows users to:

• search subjects dynamically
• search topics/content titles
• filter results instantly while typing
• navigate directly to matching subjects/topics

The implementation should:

• remain responsive and lightweight
• maintain the current UI/design consistency
• avoid unnecessary heavy dependencies

Additional Context

The search experience can be similar to simple documentation-style search systems where results appear dynamically as the user types.

Potential areas to include in search:

• subject names
• module names
• topic headings
• documentation pages

[sneharam543]

Hi @pushkarscripts, I’d like to work on this issue under GSSoC'26.

I went through the current project structure and explored how subjects and chapter routes are organized across the platform. My plan is to implement a lightweight global search feature that fits naturally into the existing navigation flow without introducing unnecessary complexity.

Approach I’m planning to follow:

• create a structured searchable dataset for subjects and chapter/topic titles
• integrate a reusable search component into the navbar
• implement instant client-side filtering as users type
• provide direct navigation to matching subjects/topics through a responsive dropdown UI
• keep the implementation lightweight, scalable, and consistent with the current design language

I’ll also make sure the search experience works smoothly across different screen sizes and remains easy to extend as more subjects/content get added later.

Please assign this issue to me if the approach looks good.

[aryanm9026]

Hi @pushkarscripts, I see @sneharam543 has already asked to work on this, but I am very interested as well! If they end up not taking it or if you need an extra set of hands on it, please let me know. I'd be happy to jump in.

[pushkarscripts]

Hi @pushkarscripts, I’d like to work on this issue under GSSoC'26.

I went through the current project structure and explored how subjects and chapter routes are organized across the platform. My plan is to implement a lightweight global search feature that fits naturally into the existing navigation flow without introducing unnecessary complexity.

Approach I’m planning to follow:

• create a structured searchable dataset for subjects and chapter/topic titles
• integrate a reusable search component into the navbar
• implement instant client-side filtering as users type
• provide direct navigation to matching subjects/topics through a responsive dropdown UI
• keep the implementation lightweight, scalable, and consistent with the current design language

I’ll also make sure the search experience works smoothly across different screen sizes and remains easy to extend as more subjects/content get added later.

Please assign this issue to me if the approach looks good.

Your proposed approach looks good to me overall and aligns well with the current direction of the platform.

Please keep the implementation lightweight and maintain the existing UI/design consistency. I would also prefer avoiding unnecessary dependencies or overly complex search systems for the initial implementation.

You can start working on this from the coding period onwards (15th May as per GSSoC guidelines). I'll assign the issue to you.

[pushkarscripts]

Hi @pushkarscripts, I see @sneharam543 has already asked to work on this, but I am very interested as well! If they end up not taking it or if you need an extra set of hands on it, please let me know. I'd be happy to jump in.

I appreciate your interest in contributing. Since the issue was requested earlier by another contributor, I've assigned it on a first come, first serve basis for now.

That said, you can still have discussions around the feature through the GitHub Discussions tab or the GSSoC Discord channel in case both of you would like to collaborate or discuss ideas related to the implementation.

Feel free to explore the other (or add) open issues as well. More contribution opportunities will be added soon.

[sneharam543]

Hi @pushkarscripts, just sharing a quick update. I’ve been working on the implementation and should have the PR ready by tonight. I had a slight delay due to some unforeseen circumstances, but the core functionality is coming together well.