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

[K7 Navigation] Improve side nav interaction and add pinnable options #30121

Closed
ryankeairns opened this issue Feb 5, 2019 · 8 comments
Closed
Labels
Feature:Home Kibana home application Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.

Comments

@ryankeairns
Copy link
Contributor

ryankeairns commented Feb 5, 2019

Several internal users/stakeholders have raised issues with the current hover-to-expand interaction on the new K7 side nav.

Following the 7.0.0 feature freeze, let's take a step back, evaluate the feedback, and come up with some alternatives. In particular, explore alternatives to using hover as the trigger and offering users the ability to pin the nav in discrete states.

cc:/ @alexfrancoeur @AlonaNadler @cjcenizal

@ryankeairns ryankeairns added Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Feb 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-design

@ryankeairns ryankeairns added the Feature:Home Kibana home application label Feb 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@alexfrancoeur
Copy link

@ryankeairns last we spoke, you were exploring some user testing I believe. Anything we can do to help here? I want to make sure we have the best experience with our nav out of the gate in 7.0. Please let myself or @AlonaNadler know if there is any way we can help.

@ryankeairns
Copy link
Contributor Author

ryankeairns commented Feb 21, 2019

@alexfrancoeur I built a couple of codesandbox prototypes for the side nav (with no content) and now I'm working on the home page/add data/guides designs which will also end up as a prototype (with real or fake content). My plan is to test those things together. More specifically - do a test around the home page/add data experience and see how the navigation performs (as-is and with the changes in the codesandbox), perhaps as early as next week.

Out of curiosity have you received any additional feedback since that additional delay was added?

@cjcenizal
Copy link
Contributor

@ryankeairns For the ES-UI team, the navigation makes it difficult to access our apps. It hides our subnavigation, which can be quite frustrating when coming from another part of Kibana. We run into this daily. Here's a screen-cap showing how I click on Management and then try to go to Watcher, but the nav opens up and blocks the mouse:

annoying_nav

@ryankeairns
Copy link
Contributor Author

Thanks @cjcenizal , that is the biggest pain point I've noticed as well. The prototypes I mention above move away from using hover as the trigger and it seems inevitable that we'll do away with that interaction. Now, it's zero-ing in on the new solution which is where we need the user testing.

@cjcenizal
Copy link
Contributor

Thanks @ryankeairns! That's great to hear. Let us know if you'd like us to act as guinea pigs.

@cchaos
Copy link
Contributor

cchaos commented Dec 11, 2019

We've taken care of the hover action and there's a duplicate issue for the pinning ability #25738. So I'm closing this one.

@cchaos cchaos closed this as completed Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Home Kibana home application Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.
Projects
None yet
Development

No branches or pull requests

5 participants