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

[Global Search Bar] Updated placeholder text to be more directive #127903

Merged
merged 7 commits into from
Mar 21, 2022

Conversation

cchaos
Copy link
Contributor

@cchaos cchaos commented Mar 16, 2022

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)

Screen Shot 2022-03-17 at 15 12 38 PM

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.

image

Checklist

And fixed search bar’s width on smaller screens
@cchaos
Copy link
Contributor Author

cchaos commented Mar 16, 2022

@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?

@cchaos cchaos added 8.2 candidate considered, but not committed, for 8.2 release Feature:Navigational Search Global search bar labels Mar 16, 2022
@cchaos
Copy link
Contributor Author

cchaos commented Mar 16, 2022

Bringing over a suggestion from the originating ticket:

Would also add that helper shadow text for the global search bar would make user discovery of the global search bar more likely (i.e. display a sample of suggested search terms prior to user entering text in that global search box)

If we go that route, it can't be a sample only. My suggestion would then be something longer-form like:

Find any Kibana page, ex: Discover

@elizabetdev
Copy link
Contributor

@cchaos and @gchaps I like how GitHub uses the "jump to". It makes it very clear that we can use the search bar to navigate to a page.

Screenshot 2022-03-16 at 19 04 18

@gchaps
Copy link
Contributor

gchaps commented Mar 16, 2022

The global search bar allows you to search both apps and objects. So maybe we should be more specific:

Find any app, dashboard, visualization, or object

Find any app, dashboard, visualization, or object. Ex: Discover

Find any app or object. Ex: Discover or visualization

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.

@cchaos
Copy link
Contributor Author

cchaos commented Mar 16, 2022

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.
Screen Shot 2022-03-16 at 16 32 48 PM

We just need them to click into the search input first. I also want to be weary about being too Analytics heavy with dashboard and visualization. But since Discover is our most used application/solution I like calling that one out specifically. How about just:

Find any app or object. Ex: Discover

@gchaps
Copy link
Contributor

gchaps commented Mar 16, 2022

Good point about not being too Analytics heavy.

+1 to

Find any app or object. Ex: Discover

@cchaos cchaos marked this pull request as ready for review March 16, 2022 21:20
@cchaos cchaos requested review from a team as code owners March 16, 2022 21:20
@cchaos cchaos added release_note:skip Skip the PR/issue when compiling release notes v8.2.0 and removed 8.2 candidate considered, but not committed, for 8.2 release labels Mar 16, 2022
Copy link
Member

@Bamieh Bamieh left a 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

Copy link
Contributor

@mdefazio mdefazio left a 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!

@ryankeairns
Copy link
Contributor

ryankeairns commented Mar 17, 2022

@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'

@cchaos
Copy link
Contributor Author

cchaos commented Mar 17, 2022

@gchaps Thoughts on Ryan's suggestion: Find apps and objects. Ex: Discover?

@gchaps
Copy link
Contributor

gchaps commented Mar 17, 2022

+1 to Ryan's suggestion to remove the word any.

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".

@ghudgins
Copy link
Contributor

sounds good to me

@cchaos
Copy link
Contributor Author

cchaos commented Mar 17, 2022

I'm more concerned about the placeholder text and getting people to notice the search input itself. I'll remove the any.

@alexfrancoeur
Copy link

Regarding the new placeholder text, I'm not sure if we should use the word objects. In my experience, non-administrators are not necessarily aware the things like dashboards are indeed saved objects. Related, do we refer to plugins and embedded views as apps consistently in our docs? I'm going to need some help here, but there are some potential alternatives with a quick brainstorm below. I don't mean to overcomplicate this, so if other folks feel confident with the current proposal, I'm happy to get on board with it.

  • Find apps and content. Ex: Discover
    • I get why we're choosing to make this very specific, but I also am hopeful that we'll make more progress on navigational search so that someday, it is not just for these two things. Technically, it's already more as we are providing direct navigation to sub views in applications. Is there a way we can make this more obvious without being so specific?
  • Find apps and saved content. Ex: Discover
  • Search to navigate.. Ex: Discover
  • Search or jump to.. Ex: Discover
    • That's blatantly copying Github, but I agree with @miukimiu, it's direct and gets the point across.
  • Jump to.. Ex: Discover
  • Navigate to.. Ex: Discover

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.

@cchaos
Copy link
Contributor Author

cchaos commented Mar 17, 2022

future product tour

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.

@gchaps
Copy link
Contributor

gchaps commented Mar 17, 2022

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.

Find apps, content, and more. Ex: Discover
Find apps, content,.... Ex: Discover
What are you looking for? Ex: Discover

My preference is the first one.

@gchaps
Copy link
Contributor

gchaps commented Mar 18, 2022

Let's go with this:

Find apps, content, and more. Ex: Discover

Here is my reasoning:

  • It adds a suggestion of what the user can find, but also indicates that there's more
  • Find is is the action that the user is taking. It's better than "Jump to..." because that's just describing basic link functionality.

@cchaos
Copy link
Contributor Author

cchaos commented Mar 18, 2022

@elasticmachine merge upstream

@cchaos
Copy link
Contributor Author

cchaos commented Mar 21, 2022

@elasticmachine merge upstream

@cchaos
Copy link
Contributor Author

cchaos commented Mar 21, 2022

I'm setting this up for auto-merge unless someone objects.

@cchaos cchaos enabled auto-merge (squash) March 21, 2022 16:34
@alexfrancoeur
Copy link

Find apps, content, and more. Ex: Discover

LGTM 👍

@cchaos cchaos merged commit bdc08fb into elastic:main Mar 21, 2022
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
globalSearchBar 19.6KB 20.7KB +1.1KB

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 23, 2022
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 127903 or prevent reminders by adding the backport:skip label.

@cchaos cchaos added backport:skip This commit does not require backporting and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Mar 23, 2022
@cchaos cchaos deleted the global_search/placeholder_text branch March 23, 2022 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Navigational Search Global search bar release_note:skip Skip the PR/issue when compiling release notes v8.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants