To put the priority of this item even lower, if going for static in T287175: Decide on most suitable underlying technical platform implies that searching would be way harder.
Plus search versus translation (T276700: Content localization infrastructure setup (export, import, deploy) which is more important than this very task) opens questions on indexing, stemming, etc.
What if that language was only 50% translated, would that lead to incomplete search results? Or search in both English and that other language?

It seems like we have a nice search functionality in the current portal, but there appear to be duplicates in the results. Maybe a bug?

In T287493#7649980, @TBurmeister wrote:

It seems like we have a nice search functionality in the current portal, but there appear to be duplicates in the results. Maybe a bug?

The duplicates are very likely untranslated "Spanish" versions of the pages. Currently there is no separation of the lunr search index content by content language.

In T287493#7650042, @bd808 wrote:

In T287493#7649980, @TBurmeister wrote:

It seems like we have a nice search functionality in the current portal, but there appear to be duplicates in the results. Maybe a bug?

The duplicates are very likely untranslated "Spanish" versions of the pages. Currently there is no separation of the lunr search index content by content language.

This example search https://developer-portal.wmcloud.org/?q=machine+learning returns:

• /build-tools/automate-editing/#use-machine-learning-to-detect-vandalism
• /use-content/data/#use-machine-learning-to-detect-vandalism
• /es/build-tools/automate-editing/#use-machine-learning-to-detect-vandalism
• /es/use-content/data/#use-machine-learning-to-detect-vandalism
• /use-content/#access-data-and-analyze-wikis
• /es/use-content/#access-data-and-analyze-wikis
• /grow/tech-capacity/
• /es/grow/tech-capacity/
• /grow/
• /es/grow/
• /#grow-your-technical-skills
• /es/#grow-your-technical-skills

Each URL here is unique. Some of the matched content is duplicate because the same document descriptor is present in multiple categories and thus multiple target pages. And then as postulated everything is repeated in the /es/ namespace due to a lack of content translations at this stage of site preparation.

@bd808, is it possible to have multiple lunr search indexes, one for each language, and search just that index based on the current language?

In T287493#7862260, @apaskulin wrote:

@bd808, is it possible to have multiple lunr search indexes, one for each language, and search just that index based on the current language?

It should be possible with custom development work, but no it is not currently possible.