-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Global Search Bar] Updated placeholder text to be more directive #127903
Conversation
And fixed search bar’s width on smaller screens
@gchaps: I'd love your input on this placeholder text. We received feedback that "Search Elastic" is confusing. So we want a more targeted "What can you search for" placeholder text. @ghudgins @alexfrancoeur: Any other thoughts? |
Bringing over a suggestion from the originating ticket:
If we go that route, it can't be a sample only. My suggestion would then be something longer-form like:
|
The global search bar allows you to search both apps and objects. So maybe we should be more specific:
Is there a place we can put the examples other than in the search placeholder text? Then maybe we could include some more examples from here. |
Thanks @gchaps. The problem is not the lack of examples or knowing how to use it, but actually finding it to begin with. There is already help text in the bottom of the popover that explains how to search for particular objects. We just need them to click into the search input first. I also want to be weary about being too Analytics heavy with
|
Good point about not being too Analytics heavy. +1 to
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(code only review) LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Nice addition of the keyboard shortcut!
@alexfrancoeur this may be nitpicky, but only apps and objects that have been 'subscribed' to the search will be searchable. For apps, it's probably close to all but for objects, it is less clear to me which have and have not yet been added. It was a struggle at the time and was left open to individual teams. That being the case, maybe tweak to 'Find apps and objects. Ex: Discover' |
@gchaps Thoughts on Ryan's suggestion: |
+1 to Ryan's suggestion to remove the word Back to the earlier point about not being too Analytics heavy, does the text in the "No results found" popup need to change too? It currently says "Try searching for applications, dashboards, visualizations, and more". |
sounds good to me |
I'm more concerned about the placeholder text and getting people to notice the search input itself. I'll remove the |
Regarding the new placeholder text, I'm not sure if we should use the word
Alternatively, if discoverability is the issue I'm not confident that simply changing the text will help here. Thoughts on opening an follow up issue that maybe introduces a feature call out? We'd have to do it at the right time in the customer journey, and maybe it's part of some future product tour, but this is a significantly faster way to get around and it'd be great to raise awareness with our user base. |
Yes! We should have done this in the first place. But let's not bungle this PR with that right now. I think it needs to be as specific as the first three options. The rest are too ambiguous. |
In the docs, we avoid using the word "app" for the reason given. We refer to things by their name, for example, Discover, Visualize. I still like the word "apps" here. And also "content". How about adding "and more" or an ellipsis to indicate it's more that just those two things.
My preference is the first one. |
Let's go with this:
Here is my reasoning:
|
x-pack/plugins/global_search_bar/public/components/search_bar.tsx
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
@elasticmachine merge upstream |
I'm setting this up for auto-merge unless someone objects. |
LGTM 👍 |
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
We've received feedback that the current visibility of the global search bar is too low and the placeholder text is confusing. This PR specifically tackles updating the placeholder text to be more Kibana-specific.
New placeholder:
Find apps, content, and more. Ex: Discover
(screenshot below is slightly out of date)In EUI, there is a separate PR to increase the contrast of the text to make is more visible. elastic/eui#5724
This PR also adds the keyboard shortcut as an
append
of the search box to more easily find and fixes search bar’s width on smaller screens.Checklist