-
Notifications
You must be signed in to change notification settings - Fork 45
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
Implement Algolia Search #633
Comments
@damassi, done. |
I started looking into this. I found a Gatsby plugin to wire it up for us. It works great on initial page load, but once you start clicking around to different routes, it loses the ability to search. I found an issue that is kind of similar, but slightly different..but it does have a lead that I'm planning on investigating today. |
I believe this is tied to component organization in Palette, rather than the plugin; on route change the sidebar is re-rendered. Lets pair if there are any issues. |
From Algolia customer support:
Congratulations, your search is now ready!
I've successfully configured the underlying crawler and it will now run every 24h.
You're now a few steps away from having it working on your website:
to a CSS selector that targets your search input field.
(See https://community.algolia.com/docsearch/styling.html)
(See https://github.com/algolia/docsearch-configs/blob/master/configs/artsy_palette.json).
Please open a pull request if want to leverage your configuration!
Feel free to get back to us if you have any issues or questions regarding the integration.
We'd also be happy to get your feedback and thoughts about DocSearch - so we can continue to improve it.
Have a nice day :)
@zephraph - would you mind logging into Algolia admin with your email (per the above) and updating to artsy@it?
The text was updated successfully, but these errors were encountered: