Right now there are validations (for example I can’t leave the First Name) empty but even if I enter a single alphabet it allows me to register.
The input value of age can be negative in the form. That’s again an issue.
Most of the dropdowns have limited data. Even I had mentioned it on the issue that I opened on github Issue
Right now there are only 4 mandatory fields and after filling them I can save the form (that does not include the submission of ID Proofs )
Then after fixing the issues. I will move to design the UI of the form. For this I will start fixing with small components and then finishing the whole page. Also I wanted to suggest As we are using material UI so we can even include MUI Forms to make it more interactive.
Thanks for the suggestions!
The drop downs you mention are just some defaults (dropdowns are called lookups in primero terminology) and they are usually modified to suit the local context for the specific Primero implementation (Government, Country, Refugee Camp etc) and/or the specific agencies (UNICEF, UNFPA, IRC, Save the Children etc) who are doing the roll out.
This fine tuning is usually done by an admin and that interface allows forms and geographical locations to be modified too (as well as the lookups I mentioned).
The user customization GSoC idea actually mentions something like this for the UI too:
The dashboard you see is based on your role in the system. So an admin will see a different interface than a case worker or regional focal point for example
I am not sure if I understand which UI you are referring to.
As v2 is still in development it may be the case that some of the items you mentioned in your first post will be fixed during the natural v2 progress towards release. As such its probably not the best use of your time to be working on them now
Maybe lets take a step back and think a bit about the focus of this GSoC idea:
front end user customization (skins) that allow improvements to the application’s design and experience
How should we approach that? How could this be implemented? What ideas do you have from other projects and so on.
Hi @irlawrence! I have looked at the doc link you have shared and I did some research as well. What I learnt about the project is:
Through User Customisation, we plan to enable users to customize or make changes to the experience to meet their specific needs by configuring layout, content, or system functionality. Through this users make their own selections about what they want to see or set preferences for how information is organized or displayed.
For an example consider these:
We can use a third-party library like “react-avatar” through which a list of avatars will be displayed and the user can select which one they want to opt for their profiles
For skins, we can think of different modes like light and dark themes.
I like this and I think we can go even further!
If a government implements Primero they often need it to fit in with existing designs - the same with implementing agencies like IRC and so on who have brand guidelines etc.
So how can they quickly change colours, logos etc without needing to do something like this?
How can this be implemented? Do you know any React / Material UI projects who have done something like this? Is there any best practices? Have you ever done anything like this before? Is this too big to manage in GSoC? etc etc
Hi @irlawrence. So can I start with proposal now as tomorrow is the last date for submission! Also, Can you tell me who all will be mentoring this project as I have to mention about it in the proposal according to the template provided by DIAL.
Also I want to discuss the project timeline because this is the thing that I can only write after discussion with the mentor. I am already on a time crunch. Please help me.