v2 search UX

[slorber]

Description

We need to figure out a good search experience for v2 site.

@Simek I'll let you explain the exact need, but as far as I understand, if a component exist in v0.63 and not in v0.64, we should still be able to search it while browsing 0.64

There's an Algolia option that could be useful for that: https://www.algolia.com/doc/api-reference/api-parameters/optionalFilters/

But I see 2 problems:

• older versions (< 0.55) are archived, so they won't appear anyway
• afaik optionalFilters will not filter duplicates across versions, which may produce weird search results

This is also related to a broader docusaurus subject where we should allow contextual search. If a user is in v0.62 we should probably present him v0.62 search results in priority (facebook/docusaurus#3396)

[nearestnabors]

Is this behind the duplicate entries here?

Personally, I feel the search bar should only search the version you're on. Using an older version? Switch to that version, use that search bar. But, was there a conversation about this with points already?

[slorber]

Hi @rachelnabors

Yes this is related to this duplicate entries problem here, and should be solved with facebook/docusaurus#3396

I also like the idea that you only search the current version you are on, as it's simpler, and expected, so if you validate this behavior it's easier for us to add this to RN website v2.

But it's not the current legacy v1 behavior, that keeps pages of older versions around (which has also been reported by some v1 users as a long standing bug, not a feature). @Simek mentioned that it might be important to be on v0.64 and be able to search for deprecated features from v0.56 etc, which is an unintended consequence for the legacy v1 behavior. If we can avoid being retrocompatible on this behavior, its better for me 😅

[slorber]

Contextual search merged, new release coming soon:

facebook/docusaurus#3550