question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[RFC] Search experience for new product spaces

See original GitHub issue

Why?

We are about to have more than 1 space in the docs that can have similar headings. If we don’t do anything, the search result will show a list of the same name (with different URL), for example:

By searching “Button”, we might see

  • Button (/material-ui/react-button/)
  • Button (/joy-ui/react-button/)
  • Button Unstyled (/base/react-button-unstyled/)

Goal

build a good-enough search experience for new spaces so that we can make them live as soon as possible

Requirement

  • search result should be ranked as the most related content
  • search result should show some differences for the same title

Proposal

The first step I think is to rank the product space based on the user’s URL.

Product space ranking

Scenario 1: on homepage When they search for “tutorial”, there is no ranking so the search result is ranked based on the object ID (default by algolia).

Scenario 2: inside a product space If they are in material-ui space (/material-ui/*), when they search anything the result of the material-ui space should be ranked first.

Product space indicator

It is possible that the search result will show the same title like:

search for “Button”:

  • Button (/material-ui/react-button/)
  • Button (/joy-ui/react-button/)
  • Toggle Button (/material-ui/react-button/)
  • Toggle Button (/joy-ui/react-button/)

To make it obvious, there should be a product identifier (like a badge after the title)

image

Product exclusion

This one is optional if we found out it is needed. Basically for the case where developers are in material-ui space should not see the search result from another design system (joy-ui).

cc @mui/core @danilo-leal @samuelsycamore

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:4
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

2reactions
danilo-lealcommented, Mar 4, 2022

That could work! Might as well iterate on this and see how it feels. @siriwatknp Any thoughts?

1reaction
oliviertassinaricommented, Mar 14, 2022

@siriwatknp 👍 for option 2. Why? Because 1 would create too much noise (need to filter the list) and because 3 could create product confusion (the same component in two different products that behaves differently).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Product Manager - RFC project - Sourcegraph handbook
More people can collaborate at once without clashing. RFCs are easily searchable and referable. RFCs are retained indefinitely. When to use an RFC...
Read more >
Informational - » RFC Editor
Number Files Date Status RFC 9337 HTML, TEXT, PDF, XML December 2022 Informational RFC 9320 HTML, TEXT, PDF, XML November 2022 Informational RFC 9317 HTML, TEXT,...
Read more >
RFC 2616 HTTP/1.1 - IETF
It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and...
Read more >
[RFC] OpenSearch.org search functionality #1219 - GitHub
Consistent experience across geographies : The search experience should ... Easily to scale the backend, upgrade to new OpenSearch versions ...
Read more >
A thorough team guide to RFCs - LeadDev
Pro-tip: Write your first RFC on implementing RFCs. It's a great way to kick the tires of your tooling, experience your own process,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found