Improve search response

[erquhart]

Requirements

• A limited number of results appear in a dropdown directly beneath the search input while typing
• Pressing enter takes you to a full results view

[tech4him1]

@erquhart Can you explain why this was closed? I still think it is unclear that you have to push enter to search.

[erquhart]

Busted. Maybe we just shouldn't have an enter button at all, just a 1 second debounce (in case an integration is in use).

[tech4him1]

I would be fine with an instant search like you mentioned, because of the small usable space we have, although I still think that is less clear.

[erquhart]

Ideally I think it would look like this for all backends:

• A limited number of results appear in a dropdown directly beneath the search input while typing
• Pressing enter or clicking submit takes you to a full results view

[mittalyashu]

Use the standard button from React Toolbox

What's React Toolbox?

[erquhart]

That's an old comment, we used to use a library called React Toolbox but it was removed in 1.0.

[mittalyashu]

Why we need a "Search" button?

Even the GitHub doesn't have a search button.

[erquhart]

Many interfaces don't, it's a fair point.

[tech4him1]

I think we should have one of two things here:

• Instant search
• A search button

Right now, if I go to type in the search box and don't think to press "Enter", I get nothing: no feedback at all on what do do.

[mittalyashu]

I agree with @tech4him1, we should go for instant search instead of a search button. As every user want the information ASAP, without doing much work and that's why instant search will be more useful.

As we are discussing search, how about we add Algolia, where users can add API keys and search bar will be replaced with Algolia search bar. Where users can not only search the title, but also the content inside each post.

[erquhart]

Instant search is a more intuitive approach. Submission is implicit, which is why I created this issue in the first place, but it's a common enough pattern that it shouldn't be a problem.

There's a custom Algolia integration already in the CMS, it just isn't a public feature yet. That's pending backend/integration API redesign work that's currently underway.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.