Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No feedback on no search results #514

Closed
h-enk opened this issue Oct 15, 2021 · 2 comments · Fixed by #517
Closed

No feedback on no search results #514

h-enk opened this issue Oct 15, 2021 · 2 comments · Fixed by #517

Comments

@h-enk
Copy link
Member

h-enk commented Oct 15, 2021

Description

When there are no search results, no feedback message is displayed.

Steps to reproduce

  1. Browse to https://doks.netlify.app/docs/prologue/introduction/
  2. Search for 22
  3. Hit Enter

Expected result

Something like:

Snag_30638fd

Actual result

No results:

Snag_303f40e

After hitting Enter:

Snag_30404d7

Environment

Not relevant.

@schnerring
Copy link
Contributor

schnerring commented Oct 15, 2021

From the Algolia docs:

The most common autocomplete UX is one that displays a list of suggested searches that your users can select from as they type. Algolia provides a Query Suggestions feature that generates suggested search terms based on your what your users are searching for and the results within your dataset.

Although flexsearch provides query suggestions, what you're looking for here is (user-)data-driven query suggestions which is typically done with analytics services.

So unless there is a way to statically build search suggestions, I don't know how to get around an external service provider like Algolia.

@h-enk
Copy link
Member Author

h-enk commented Oct 15, 2021

Yeah, I get that. I don't think we should go down that road. Data or user driven query suggestions are not a must have for Doks (as far as I'm concerned).

However, I think it would be user friendly to show a message "No results for "<search term>"", instead of showing nothing at all. Do you think that's feasible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants