go-frontend
go-frontend copied to clipboard
IFRCGo
UI improvement for GO backend
Confusing layout and unclear navigation for the django backend inhibits new users from understanding different functions in the GO application.
User-centred design process required to address core user interactions.
The goal of this task is for the design team to review where the external users need to access the back-end and how to bring those features to the front-end (similar to existing forms) in a coherent way. The pure back-end functionality will remain only for the admins.
The process will include review of the platform, understanding various use cases of access from the team and a design proposal.
@LukeCaley @tovari We did quite a thorough audit of the back-end (based on staging) and also front-end forms: https://docs.google.com/spreadsheets/d/1kbcTIqchfmpOtBCAYg5zTJHfgCC6dVZF_jfxe81nTII/edit?usp=sharing
We have a lot of questions for some things, as well as user permissions and such. So, would be good to dig deeper. Overall, here is the gist of our suggestions:
- Region, country, specific emergency page edits should be updated on the front-end
- 3W is front-end but needs to be cleaned up and more integrated with the updates
- Relevant sections need to go with relevant sections; for example, PER updates for each country should be part of the country front-end edits or deployment updates for each country should go there
- Discussing user roles, permissions and needs would help to clarify the above to know which users need to access which sections
Please let us know if this is what you had in mind for the audit, as well as any comments/questions you may have. Thank you! (cc @maisa-yu )
xref https://github.com/IFRCGo/go-frontend/issues/1357 and https://github.com/IFRCGo/go-frontend/issues/1699
