Making UI changes based on industry standards #477
Description
Description
As long as Packit dashboard has existed the design has been based on feature parity with the Packit service, with very little focus for the user experience of the dashboard itself. That is not to say the current UI is not good, but they have not been made with the goal of being user-first rather than API-first.
Current Packit dashboard has a lot of features to showcase the Packit service, but very little tooling to help teams and products get an overall view of their projects and pipelines.
To that end, when we do changes we should
- Make sure the new or changed features of Packit service have improved functionality to help the dashboard thrive.
- Create UI change suggestions based on user interviews (User interviews to align Packit dashboard with people's need #476) with a focus for reduced mental complexity.
- Get feedback on UI suggestions from experienced designers, such as those from Red Hat UXD (User Experience Design) team.
Once we have established a good system we should make sure to document it to reduce bus-factor.
Benefit
Users of Packit would benefit from an improved UI to help them see the results they need for the pipelines they run as well as for the project or product they manage.
Importance
It is very important to make changes to the UI with industry standards that has been established by designers in the software industry. Packit is no different, so to that end it is crucial that changes are made with users in mind.
We do not need to get feedback from designers for every suggestion, nor do we need mockups for every change. But for reducing complexity or adding new big features we should make sure to have a good direction for it.
Workaround
- There is an existing workaround that can be used until this feature is implemented.
Participation
- I am willing to submit a pull request for this issue. (Packit team is happy to help!)