-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI: High-fidelity Mockup - Register #2
Comments
Update: I'm no designer so I know this is far from ideal. Please do give me your opinion on this. If you like this as it is, please give your approval by using ✅ on this post. Thanks heaps. PS: I couldn't find ways to arrange the exact distancing between components on justinmind. Still working my way around this tool While waiting I'm going to open an issue at backend repo and start working on the API endpoints and CRUD operations for this page. |
Like your design! When a user checks 'Yes' for 'Do you represent an organization?', will an extra space pop up so that the user can enter his/her/their organization? |
@mtreacy002 about the share button, we can troubleshoot this in our 1:1 this Saturday ;) Questions that came up:
|
Thanks, @isabelcosta.
Yes, because:
I would love to think so, this is so:
If the general public wants to be involved in BIT, they then need to be registered. |
@foongminwong, atm, I''m thinking that with this checkbox, if it's |
Hi @anitab-org/bridgeintech-maintainers, I have something I'd like your vote/opinion on. Or maybe you have another option? |
Note to self:
|
@mtreacy002 I like 🐨 Members :) but I'm biased since I am using that on mentorship system. I feel it's less specific about the roles of the users. Then you can specify in the item in the list thst represents a user. This is my opinion :) |
Some comments:
|
Remember to let users enter |
Update: |
Hey @mtreacy002 looks good, I however have an alternate approach. We can think of the RegistrationForm/Register as a component, when you see a repetition/duplication while creating other components, you can then extract it out to a reusable/common one. If you pre-plan this, I'm afraid we may cause a certain amount of over-engineering. So start off with one component, and wait till you see duplication to extract. |
Agree. I was actually thinking about that too... Making it as Form level (Register Form) as component will probably help make it faster to be reused rather than adding field one at a time... 😂. Thanks for the tips, @meenakshi-dhanani |
Update: To overcome the issue blocking issue#26 backend, the Register form needs to be modified as below: Can @anitab-org/bridgeintech-maintainers mentors please approve this change so I can apply the backend change accordingly. |
@mtreacy002 commented on Thu May 14 2020
Description
As a student,
I need create high-fidelity mockup for Register,
so that I can move forward with on the planning stage.
Mocks
Initial idea (per proposal)
Figure 1.1. Register
Acceptance Criteria
Update [Required]
must have all the fields for Mentorship System user registration:
[ ] name
[ ] username
[ ] password
[ ] confirm password
[ ] email
[ ] terms and conditions check box
[ ] need mentoring check box
[ ] available to mentor check box
must have
Organization
andMentor/Mentee
check boxmust have
Signup
andLogin
buttonsmust have
view/hide
password field optionsDefinition of Done
Estimation
1 day
The text was updated successfully, but these errors were encountered: