feat(search): surface explorer views in search results

[marcelgerber]

TODOs

• Implement card-based design
• Do grouping by explorerSlug
• Do client-side deduplication based on [viewTitle, explorerSlug]
• Add click tracking
• maybe do country name removal (optionalWords)
• probably sort explorer cards with more view items higher up
• cleanup:
  • remove display of explorers index
  • remove SearchIndexName.explorers and all uses (refactor(algolia): remove old explorer indexing code #3472)
  • remove all references, styles etc.
  • css styles

[marcelgerber]

• Explorer search: Incorporate design feedback #3493
• refactor(algolia): remove old explorer indexing code #3472
• feat(search): pre-select explorer entities if they appear in search query #3483
• feat(search): surface explorer views in search results #3429 👈
• feat(search): disable fulltext pages search if we detect a country name in query #3481
• enhance(search): Search utils #3480 : 1 other dependent PR (#3388 )
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @marcelgerber and the rest of your teammates on Graphite

[marcelgerber]

Click tracking is now part of this, but it's a bit messy overall:

For posts (unchanged)

{
	query: "co2",
	position: 2, // Second overall entry
	positionInSection: 2,
	filter: "all"
}

For charts (unchanged)

{
	query: "co2",
	position: 6, // Second chart, 6th global result
	positionInSection: 2,
	filter: "all"
}

For full explorer links ("Explore all ... indicators")

{
	query: "co2",
	position: 9, // First explorer card
	positionInSection: 1,
	cardPosition: 1,
	positionWithinCard: 0, // Special marker for the "Explore all ..." link
	filter: "all"
}

For links to a view

{
	query: "co2",
	position: 14, // Second explorer card, second link
	positionInSection: 6, // Five results (links) before
	cardPosition: 2, // Card number 2
	positionWithinCard: 2,
	filter: "all"
}

Of course, the href is also always included as an eventTarget property.

Am I happy with that? Not really 🤷🏻
If anyone can come up with a better and more straightforward way then please let me know!!

[ikesau]

The functionality is overall very nice! Just a few comments on behind the scenes stuff

[ikesau]

You might want to position: absolute; margin-top: .5rem this so that it doesn't dangle

[ikesau]

With display: block; width: calc(100% - 16px); on .search-results__explorer-view-title-container to ensure there's space

[marcelgerber]

Could achieve the same thing using ‍ (zero-width joiner) and white-space: nowrap.
PR will go up soon, together with other design changes.

[ikesau]

I think this is a regression not from this PR, but it seems like data-algolia-position is now only local to each section, i.e. posts start at 1, charts start at 1, etc.

charts were meant to start at numberOfPosts + 1

[marcelgerber]

I think that's what it was meant to do, right?
data-algolia-position is the local position, and globalPosition gets computed in the click handler on its own (and only gets sent to GTM, not to Algolia).