-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[docs] Change Algolia search implementation #26112
Comments
@oliviertassinari May I work on this? |
@arpitBhalla I was thinking that @siriwatknp could be working on it, I think that he can supervise the effort, so up to him :) |
@arpitBhalla please go ahead if you like, I can help on the review and answer question if you have any. |
Thanks @siriwatknp |
@arpitBhalla Do you have any updates? This one is important for the DX on the documentation as well as our brand, this looks neglected: |
@siriwatknp @oliviertassinari Popper js website uses |
I was thinking of salvaging what we can from Maybe we could push it even further with our own components but hard to tell how without understanding how docsearch is falling short, first. It's also not clear if we have the bandwidth to make something great ourselves (it has to be above average). |
So it would be great to use |
It looks like an interesting start. Note that we will also render it in https://next.material-ui.com/branding/about/ afterwards. |
Summary 💡
Redo the integration with Algolia's API.
Examples 🌈
https://popper.js.org/react-popper/
Regarding how we will display the search bar, something we have pocked with for desktop and mobile.
Motivation 🔦
The new interface of https://github.com/algolia/docsearch is similar to Spotlight on macOS, it yields a better UX than the current one.
In the future, we could even consider internalizing this component, I have seen https://blueprintjs.com/docs/versions/4/#select/omnibar do it, but it's unlikely something we want to consider now as the objective is to do a quick win, without involving a designer.
The text was updated successfully, but these errors were encountered: