-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Search (with filters) #9
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Ok! We're going with Statamic for the rewrite, which looks like it handles search nicely. it's going to be API driven (#1) and Statamic have Algolia search built right in. I've mentioned this in the redesign considerations (#6 @ijpatricio), and I'll try and get this sorted out in the |
Statamic conversion complete! #13 Algolia has been hooked up: 1c888a5 If anyone can pick this up, base off of the |
I can work on this @philsturgeon |
Yeah, sounds good @philsturgeon |
Gonna call this one done even though its not designed yet. Thanks @Tajmaha! |
Implement a search page
/search
in the new frontend (found in thenew
branch). Our amazing new backend has search functionality which integrates with Algolia.This means we can just use the JavaScript frontend client, and the search key is
e8be8c8a25143890d82abf2108de8f93
.Please hook up the search form in the header:
I think our Algolia integration only sends the
title
andid
property, so if you're feeling adventurous you could try and get it sending tags and description, to make search find those results too, but... by no means feel obligated.Poke me for API keys.
The text was updated successfully, but these errors were encountered: