-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Epic: Improve dashboard navigation #8385
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
Comments
In the spirit of questioning the proposed designs above, here're some screenshots side-by-side of the new navigation with no, soft, and hard highlight of the active menu on a real page like the Workspaces list which also contains a primary action button. Cc @jldec @svenefftinge
|
I've updated the designs in the description to move forward with the soft highlight for this iteration. |
Removing from in-progress |
I've opened the follow-up #10976 and reopened the #7879 for keeping track of the outstanding two tasks of this epic. @jldec Sounds good to close this issue (epic) based on #8385 (comment)? |
@gtsiolis, I'd prefer to keep this Epic open since we still have 2 incomplete tasks - they're just not scheduled for immediate implementation. |
Sounds good, @jldec! Your call. 🏀 Just wanted to bring some visibility to these new follow-up issues. |
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. |
Epic tasks
Workspaces
into top right nav, moveDocs
andHelp
under profileProblem to solve
The dashboard navigation has grown over the last few months with the addition of new features like Teams & Projects as well as new features in the admin dashboard like Telemetry settings, etc.
This introduced new components like tabs and dropdowns that help scale the user interface options but also improve overall UX of the dashboard, etc. However, on the way the the additional navigation elements affected usability and more specifically user control[1] and consistency[2] across the product, see screenshots below as well as relevant issues: #7668, #7879, and #7716.
Proposal
Opening this as a placeholder issue based on the relevant discussion[1][2] (internal). Cc @jldecIn the spirit of MVC (minimum viable change) here's the proposed changes within the scope of this issue.
Changelist:
Changes to consider:
Designs
See design specs.
The text was updated successfully, but these errors were encountered: