docute
docute copied to clipboard
egoist
Build a local search plugin
Using the plugin API for searching: https://docute.org/plugin-api#apienablesearchoptions
IssueHunt Summary
Backers (Total: $200.00)
issuehunt ($200.00)
Submitted pull Requests
Become a backer now!
Or submit a pull request to get the deposits!
Tips
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on IssueHunt to raise funds.
IssueHunt has been backed by the following sponsors. Become a sponsor
Any progress regarding this functionality? I want to migrate to docute, but I don't want to use Algolia 😩
This vue component might be a good example (or potential component to integrate) to offer this: https://github.com/shayneo/vue-fuse/
Now we have a plugin API for searching: https://docute.org/plugin-api#apienablesearchoptions
We just need to figure out how to create/store search-index.json
@issuehunt has funded $200.00 to this issue.
- Submit pull request via IssueHunt to receive this reward.
- Want to contribute? Chip in to this issue via IssueHunt.
- Checkout the IssueHunt Issue Explorer to see more funded issues.
- Need help from developers? Add your repository on IssueHunt to raise funds.
Given that this runs in browser might as well run it in memory. The files would have to be loaded from sidebar, parsed-https://github.com/markdown-it/markdown-it-, and then fed into a search library such as https://www.npmjs.com/package/lunr which takes objects and appears to return the whole tree made of object keys for a result. Ideally the link would be able to take you to that exact spot in text, or at least a paragraph, something a parser might not support like paragraph 1 after h3. When markdown component loads, do those link work via router or is it something browser supports with markdown?
So is it okay if search material is compiled at runtime, instead of having search-index.json produced before then?
