Eunjae seeks feedback for Algolia search integration with Sanity

Hello people,I'm User, working for Algolia.
I'm planning a live coding to show you how to add search functionality to your website built on Sanity.

Can you give me some idea regarding search? Like some special case of yours that was hard to deal with. Or some search feature you wish to have in your website, etc. Or let me know if you have any random question
🙂

An integration with Next.js would be nice! For Example how i can use it for filtering of the Blogposts by category and the full text search? Like on this page: https://rheinstetten.tv

I was thinking of using gatsby for the live coding. Do you think it still helps you if I do it on gatsby?

Another idea is to make a showcase fo a small shop where you can filter the articles by different properties like size, color, gender and so on

Not for us. We have switched from Gastby to Next.js. It’s much more flexible and has an incremental static site generation with preview mode build in. So we would focus on Next.js in the future

Thanks for the suggestion! I'll consider nextjs. Even if I go with gatsby, I'll give you enough information to apply with your nextjs website. The very beginning part (indexing data) is different and the rest (ui) is the same, though.

Hi ! I’d recommend having a demo gatsby or nextjs site with at least 10-20 documents populated, and more if using multiple types. A couple use cases for Algolia come to mind:• Using Sanity + Gatsby/Next ( as a Help Center, and adding in help article search (this could include faceted search) and you could facet by solutions for iPhone or Android or Web as an example
• Using Sanity + Gatsby/Next to recommend similar articles at the end of reading a blog post
• Building out an online ecommerce shoe store (or other product store) using sanity + gatsby/next and searching through colors, brand, material, etc
Hope this is helpful!

Great examples, i totally agree with you!

Hey Thanks for your examples!
One question,

as a Help Center

In that example, do you mean to have a search feature on the website? or on the studio?

Hey , I was thinking search on the front-end experience. The studio comes with a document search, but I haven’t stress tested it against hundreds or thousands of documents

Okay got it. Then I feel like your example 1 and 3 are technically the same (search with facets). Or did I miss something?And I didn't think of having a recommended article section for the live coding. Good idea!

From the overall perspective that there are facets, yes they are similar, but the execution can be different. In example 1 (Help Center), you could read the device type to prefer those articles first (or to display why the result was shown), “98% match because you’re on an iPhone” or something. For example 3 I was thinking would be more complex since products have multiple fields to check against (color, brand, etc), and probably could involve a more complex checkbox style faceted search whereas option 1 could either be solely sorted based on the facet or simply use a dropdown filter. What’s more, you can use these fields to provide more intelligent smart recommendations when the user clicks into one of the results at the bottom of the page. For example, viewing black nike running shoes could show other black or dark-tone running shoes at the bottom of the page, with a preference for Nike. Ultimately, its up to you how complex you want to get and what you think will help users here understand how to integrate Algolia into their Next or Gatsby front-end

Hey User, thanks a ton for great examples. I'll see how much I can fit into an hour. This is so helpful 🙂 I really appreciate it.