Segmenting Search Results in Docusaurus Packages
TLDR Dennis sought a way to segment Docusaurus search results by package. Jason suggested forking the docsearch UI to allow for this.
1
1
Aug 10, 2023 (3 months ago)
Dennis
11:56 AMI have two packages and created a documentation (on the same docusaurus instance) for each package.
Let's say package-core and package-client.
I use the docsearch scraper to index all of the documentation.
If I use the TypeSense Docusaurus search plugin the search works as expected.
But there is no way to tell if the search result belongs to package-core or package-client, it is always listed under "Documentation".
Is there a way to split the search results like this:
package core
--- result one
--- result two
package client
--- result one for client
Jason
03:33 PMAug 14, 2023 (3 months ago)
Dennis
08:34 AM1
Typesense
Indexed 3005 threads (79% resolved)
Similar Threads
Keyword Highlighting Issue on Docusaurus with Typesense
Inas experienced trouble with keyword highlighting on a Docusaurus doc site using Typesense. After a detailed discussion, Jason clarified that the desired functionality isn't possible to implement in a cross-browser compatible way without modifications to Docusaurus core.
Configuring Docusaurus and Typesense for a Documentation Site
Apoorv had trouble adding search functionality to a Docusaurus documentation website with Typesense. Jason worked through several troubleshooting steps, identified issues with Apoorv's setup, and ultimately provided solutions that successfully implemented the search bar function.
Issue Integrating Typesense with Docusaurus Documentation Website
Oz had issues integrating Typesense with their Docusaurus documentation website, Jason suggested running the docsearch-scraper and making adjustments to the start URLs to resolve the issue.