podman-desktop / podman-desktop

Podman Desktop is the best free and open source tool to work with Containers and Kubernetes for developers. Get an intuitive and user-friendly interface to effortlessly build, manage, and deploy containers and Kubernetes — all from your desktop.
https://podman-desktop.io
Apache License 2.0
4.94k stars 314 forks source link

Move Providers to the StatusBar (Phase 1) #8922

Open Firewall opened 2 months ago

Firewall commented 2 months ago

Epic domain

As part of the dasboard and statusbar revamp we want to move all the providers that are currently on the Dashboard to the statusbar. This allows us to highlight more important items on the dashboard instead.

Is your enhancement related to a problem? Please describe

Our current Status Bar has some UX challenges:

Describe the solution you'd like

By adding all of the missing resources to the statusbar and also using a consistent pattern to display them. The statusbar will become a consist place for our users to

  1. See the status of their Resources/providers
  2. Quickly get to the settings, options

Ideas:

deboer-tim commented 1 month ago

We've been talking about reducing what's on the dashboard and adding more to the status bar and Resources in previous issues stretching back over a year now 😕. There is a lot of complexity in the dashboard provider cards today, we've tried to design it all away in one shot, and then it's too big / too many holes to implement. Plus, there are some things like notifications for provider updates that we might still want on the dashboard, just not in the current form.

My main suggestion to make more progress this time is to keep it incremental: design one useful thing in the status bar or Resources page, build it, then remove the equivalent from the dashboard, all in independent chunks to keep it manageable.

Firewall commented 1 month ago

Totally agree with that @deboer-tim. So what are the main things that the dashboard shows about the providers. 1. Status 2. Error if there are any. I totally see that as a follow up task after this one.