Skip to content

Conversation

@cameronelliott
Copy link

Added Typesense-js to the list of Search UI libraries.

Change Summary

I was try to better understand the different paths I could take to build a front end to Typesense, and I thought having the typesense-js listed here in the docs would have helped me understand the paths possible.
I understand you might not think it fits, and might not merge.
Nonetheless, I thought I would share my thoughts and suggested change.

PR Checklist

Added Typesense-js to the list of Search UI libraries.
@jasonbosco
Copy link
Member

Given that this section says "Other UI Libraries", it then feels off to include typesense-js under that list and then say it's not a UI library. May be we can add a tip section instead below it separate from the list.

@cameronelliott
Copy link
Author

That sounds like a good idea.

@cameronelliott
Copy link
Author

I want to ask a Typesense-newbie question. Is there any good page or article which compares the four primary UI solutions for Typesense?

  • InstantSearch.js
  • Typesense MiniBar
  • Autocomplete.js
  • DocSearch

I know I can ask an LLM, but someone knowledgeable has written on this topic, that's probably a much better source.

Sorry if the page/url should be obvious to me, but I don't think I have seen this comparison yet.

Thank you

@cameronelliott
Copy link
Author

One more question comes to mind, that I would like to see if I understand.
Typesense's compatibility with DocSearch is due to a fork, right? https://github.com/typesense/typesense-docsearch.js

So, DocSearch Version 4 (v4) is not really compatible with Typesense? Or do I misunderstand?
Thank you.

(PS, Typesense, is very impressive!)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants