Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fully Implement Elastic Lunr for Enhanced Tutorial Search #149

Closed
lokeshwar777 opened this issue Aug 28, 2024 · 2 comments · May be fixed by #150
Closed

Fully Implement Elastic Lunr for Enhanced Tutorial Search #149

lokeshwar777 opened this issue Aug 28, 2024 · 2 comments · May be fixed by #150

Comments

@lokeshwar777
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Yes, while the app has Elastic Lunr initialized, it's currently not being utilized. This results in an incomplete search functionality, making it difficult for users to efficiently find tutorials by search query.

Describe the solution you'd like
I would like to fully implement and integrate Elastic Lunr to enable a robust search mechanism for tutorials based on tutorial data. This solution should include:

  • Ensure Elastic Lunr is correctly initialized with the relevant fields.
  • Integrate Elastic Lunr with the existing backend to handle search queries and return the appropriate tutorial results.

Describe alternatives you've considered
Using Firestore for querying directly, but this could lead to increased costs and complexity, especially with large datasets.
Elastic Lunr offers a lightweight, client-side search solution that doesn't require additional database queries.

Additional context
Elastic Lunr is a lightweight search library that is already part of our tech stack but has not been fully implemented. By leveraging its capabilities, we can improve the search experience and make tutorials more accessible to users. This would also help in managing and scaling the search functionality as the content grows.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 28, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant