bitcointranscripts / bitcointranscripts/bitcointranscripts.github.io
Integrate Elasticsearch to Enhance Search Functionality
- Dominant language
- SCSS
- Stars
- 6
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Currently, our search functionality is limited to matching user queries with a pre-generated [index.json file](https://btctranscripts.com/index.json). [This file is created](https://github.com/bitcointranscripts/bitcointranscripts.github.io/blob/master/themes/ace-documentation/layouts/_default/list.index.json) during the build process and includes the titles and first 500 characters of each transcript. While this method provides basic search capabilities, it does not allow for comprehensive or highly relevant search results.
To improve this, we can leverage our existing Elasticsearch infrastructure, which is already in use for indexing all transcripts for [bitcoinsearch](https://github.com/bitcoinsearch/bitcoinsearch-app). This search approach is already implemented in [Bitcoin TLDR](https://github.com/bitcoinsearch/bitcoinsearch-app).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with themes/ace-documentation/layouts/_default/list.index.json and the generated index.json to understand the current search input. Then compare the existing Elasticsearch search approach in the bitcoinsearch-app and identify how it could fit this static Hugo site. Done means the site uses the existing Elasticsearch transcript index and provides more comprehensive, relevant search results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, hugo
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100