New UI: bring administrative tasks to the surface and make them relative to the context

[AlexSkrypnyk]

Hi all,

This is a thread to highlight the importance of effectiveness of the administrative tasks in Lagoon UI.

In the current UI, there are many places where information or actions that are needed are located 2-3 clicks away. Managing multiple projects with multiple environments becomes a "click-and-wait" activity that, I'm sure, people would like to avoid as much as possible.

I'm not going to provide examples here based on the current Lagoon UI. Instead, let me ask the community on the preferred approach to organising UI to make it clear and efficient.

I'm proposing to start with the following:

1. Create a poll/thread to ask the community to provide top 5 operations performed in the UI and how many clicks it takes (for example, to see the duration of the last deployment, I have to click multiple times and get to the bottom of the build to see this; I need this info to know how long will the next build take approx so that I know when I can get back to this project when the env is ready).
2. Setup user interviews with 5-10 active users and ask up to 20 UI questions
3. Post a roadmap of UI ideas along with intended designs (Figma?) so people could comment.
4. Setup early prototype testing before developing anything in code (Figma allows to create prototypes easily).
5. Define delivery milestones, so that users would know when to expect the new UI to be available.
6. Allow early access to switch to new UI.

Lastly, it may be beneficial to look at other hosting providers - Acquia has been providing dashboards for 10+ years and users liking it. CircleCi is another provider that has a lot of data available to the user, but organised in a nice way.

Thank you