Skip to content

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

Closed
5 tasks done
gtsiolis opened this issue Feb 22, 2022 · 7 comments
Closed
5 tasks done

Epic: Improve dashboard navigation #8385

gtsiolis opened this issue Feb 22, 2022 · 7 comments
Labels
component: dashboard meta: never-stale This issue can never become stale meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team type: epic

Comments

@gtsiolis
Copy link
Contributor

gtsiolis commented Feb 22, 2022

Epic tasks

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

Projects (Personal Account) Projects (Team)
Screenshot 2022-02-22 at 3 14 35 PM Screenshot 2022-02-22 at 2 41 45 PM
Settings (Project) Settings (Admin) Users (Admin)
Screenshot 2022-02-22 at 2 42 00 PM Screenshot 2022-02-22 at 3 22 42 PM Screenshot 2022-02-22 at 2 42 21 PM
Workspaces (Personal Account) Branches (Project) Prebuild (Project)
Screenshot 2022-02-22 at 2 41 33 PM Screenshot 2022-02-22 at 2 41 53 PM Screenshot 2022-02-22 at 3 26 52 PM

Proposal

Opening this as a placeholder issue based on the relevant discussion[1][2] (internal). Cc @jldec

In the spirit of MVC (minimum viable change) here's the proposed changes within the scope of this issue.

Changelist:

  1. Move workspaces as a global navigation menu item
  2. Introduce a dropdown split button with two active areas.
  3. Use the team scope dropdown left area to link to the default page of the scope, that is Projects.
  4. Use the team scope dropdown right area to trigger the dropdown.
  5. Use a darker active color to visually separate information hierarchy of the page contents below.
  6. Move the tabs (Projects, Settings, etc) below the header section.
  7. Re-structure admin menu to use tabs.
  8. Move Help and Docs user menu inside the user dropdown as described in Epic: Low-friction dashboard form to collect feedback #7925 (comment).

Changes to consider:

  1. Keep the active top-level menu item per page. ✔️
  2. Use a narrower container width (optional).
  3. Use more radius for the top-level navigation menu items. ✔️
  4. Remove the separator border between the top-level navigation and the header title. (would help to show top-nav everywhere)
  5. Consider moving the feedback menu inside the user dropdown.

Designs

Workspaces
Workspace-Active (AFTER)
Broad width Narrow width
Workspaces-1 Workspaces
Team Hover (Left) Team Hover (Right) Team Active
Team-Hover Team-Hover-1 Team-Active
Project Prebuild Admin
Project Prebuild Admin

See design specs.

@gtsiolis
Copy link
Contributor Author

gtsiolis commented Mar 8, 2022

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

No highlight Soft highlight Hard highlight
1 2 3

@gtsiolis
Copy link
Contributor Author

I've updated the designs in the description to move forward with the soft highlight for this iteration.

@jldec
Copy link
Contributor

jldec commented Jun 20, 2022

Removing from in-progress

@gtsiolis
Copy link
Contributor Author

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

@jldec
Copy link
Contributor

jldec commented Jul 12, 2022

@gtsiolis, I'd prefer to keep this Epic open since we still have 2 incomplete tasks - they're just not scheduled for immediate implementation.

@gtsiolis
Copy link
Contributor Author

gtsiolis commented Jul 12, 2022

Sounds good, @jldec! Your call. 🏀

Just wanted to bring some visibility to these new follow-up issues.

@gtsiolis gtsiolis removed their assignment Jul 25, 2022
@stale
Copy link

stale bot commented Nov 9, 2022

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.

@gtsiolis gtsiolis added the meta: never-stale This issue can never become stale label Nov 9, 2022
@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Nov 9, 2022
@stale stale bot closed this as completed Nov 26, 2022
@stale stale bot moved this to In Validation in 🍎 WebApp Team Nov 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard meta: never-stale This issue can never become stale meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team type: epic
Projects
Status: In Validation
Development

No branches or pull requests

2 participants