Issues with migrating search from Algolia to Typesense

Nacho

just noticed this url goes nowhere, does anyone have the updated link?

Jason

Oops, it should be this:

Jason

Will fix that comment

Nacho

awesome thanks, sent you a DM here in slack but I already found my way mostly

Nacho

will ask here if any more questions arise

Nacho

running the scraper now

Jason

I was just typing this out… We don’t have a migration guide for Docusaurus per se, because it’s just a “fresh new integration”, when you follow that step-by-step guide which you’re following

Nacho

yep perfect

Nacho

where do I access the features you showed of pinning and synonyms and such?

Jason

It’s under “Curation” on the left panel

Nacho

oh right it was greyed out because I was still scrapping whoops

Nacho

okay will take a look scrapping it’s getting there already

Nacho

okay how do I now replace the algolia search with the typesense search? I feel like I did here but I might be missing something else?

Nacho

sorry if it’s a noob question :smile:

Jason

Yup that should be it

Nacho

well for some reason it wasn’t, I’m still seeing the algolia search on my preview url

Nacho

Nacho

but no results :smile:

Nacho

which makes sense since I removed my algolia key and such

Jason

Is it showing up locally?

Jason

Another thing to try, is first turning off the Algolia search bar completely

Jason

Make sure that works as expected, without any errors

Jason

And then install the typesense theme

Nacho

hmm

Nacho

how do I do that?

Jason

Looks like just removing the `algolia` key from the docusaurus theme config might do it?

Nacho

hmm seems like we have some config on top that might be it

Nacho

seems like we had a custom component to show algolia that’s why it was showing

Nacho

but after removing it, not sure how to get back to the default so typesense would show by default

Nacho

(as you can see, I didn’t set this up initially)

Jason

Ok once you’ve removed it, does the search bar disappear locally?

Nacho

yes

Jason

Ok cool

Jason

Now if you add the typesense specific config and theme, does it show up now?

Nacho

didn’t remove it, do you want me uninstall the theme and add it again?

Jason

Did you restart the docusaurus dev server?

Nacho

this was the culprit

Nacho

yeah

Nacho

I think the problem is that we’re rendering a custom navbar

Nacho

so that might be out of scope for you

Jason

Yeah, and also out of my docusaurus knowledge :sweat_smile:

Nacho

I’ll figure it out, will update :smile:

Nacho

well now I have the search, just need to have the things I had in my navbar back

Jason

That was fast!

Nacho

yeah just had to delete the component

Nacho

basically because I had a SearchBar component, it was getting replaced

Nacho

okaaay all fixed

Nacho

Nacho

now onto the fun stuff with personalization and setting the github action

Nacho

my scrapper has been running for like 90 mins I feel like

Nacho

oh just finished

Nacho

any idea why some results instead of sending me to the page they sent me here?

Nacho

(see url)

Jason

Could tell me the search term that generates those URLs?

Nacho

“ui components”

Jason

The first two links in the search results essentially point to the home page, and that tile doesn’t have any anchor / link to point the user to

Nacho

ohh so that’s what it’s getting linked to

Jason

yup

Jason

I’d recommend excluding the home page from search results

Nacho

yeah, did with base config first to start

Nacho

not sure why it doesn’t find this page

Nacho

how do I exclude homepage?

Jason

Nacho

the config file is incredibly cumbersome

Jason

You want to use `stop_urls`

Nacho

so just `"stop_urls": [` `"/tests", "/"` `],`

Nacho

?

Nacho

add the “/”

Nacho

oh no\

Nacho

that wont work

Jason

Might have to use regex to make sure it only matches the home page

Jason

That’s because is set to `header h1`, but on that page there’s no dom element like that You want to change that to `article h1, header h1`

Nacho

that was exactly what I was looking at

Nacho

also, does this look correct to you?

Nacho

Nacho

in the hierarchy sense

Nacho

what’s important is the “useContract() function”

Nacho

and that’s hierarchy lvl2

Nacho

(getting deep now in the config stuff)

Jason

In the Typesense Cloud dashboard, it by default searches only the first 3 fields. But in docsearch there’s a specific field priority order defined

Jason

So what you see in the actual docsearch UI will return results in that priority order, which will be different from what you see in the dashboard….

Jason

Unless of course you setup the dashboard to mimic those same settings used in docusaurus

Nacho

not sure I follow

Nacho

so my results in the cloud dashboard will differ to what I see in my site?

Nacho

that’s what you’re saying right

Jason

correct

Jason

If you scroll to the bottom of the search page in the cloud dashboard, you’ll see the search settings used

Jason

Those are different from what the docusaurus-typesense plugin uses at runtime

Nacho

right, and how do I sync them? I can do that with the preset thing you told me right?

Jason

Yup!

Jason

I would recommend starting out with the default config from the docsearch plugin. If you look at the network requests sent to Typesense in the browser’s dev console, you’ll see all the default values for all the search parameters

Nacho

I feel like prioritizing lvl2 is what’s giving me best results

Nacho

but that might be a problem with how stuff is set up in docusaurus?

Jason

You could try changing it and see what the impact is…

Nacho

because pages like this

Nacho

the title is an h2

Nacho

when it should be an h1

Nacho

sorry if I’m bothering you with my thoughts here

Jason

I’d recommend updating the markup if that’s an option

Jason

No worries!

Nacho

hmm yeah that might be an option I need to check the autogeneration

Nacho

okay let’s say I can’t do that (not sure yet)

Nacho

if I say okay I want this

Nacho

how do I set it up on docusaurus to be like this?

Nacho

I create the preset

Nacho

Jason

Then in this line, you’d add that preset name:

Nacho

do you have an example? I don’t see preset on any of the examples

Nacho

also, is this scoped to _everything_ or can I do only for certain url scopes like with the hieararchies?

Jason

This will be scoped to everything…

Jason

I don’t have an example unfortunately

Nacho

do you think someone can get me one? :smile: not sure what the syntax is supposed to be

Jason

`typesenseSearchParameters: {"preset": "lvl2-priority"}`

Jason

In

Nacho

okay nice awesome

Nacho

thanks