Guest Registration UI/DB Team Collaboration
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
Summary
I've noticed some conflicts between the UI and DB teams that we should get on the same page about before moving much further along. Us in the UI team have some new ideas on how to implement the UI that will effect where/what you guys are pulling from/entering into the database. I'll list the major ones below:
- More Fragments - The original plan on here was 2, the teacher suggested 4. We're leaning towards at least 4. The idea is to not have the user scroll when putting in info, make it interactive, and allow enough space for the fields/buttons. We'll have to flesh out exactly how many.
- Verification - In the original plan, they verify at the very end using the person's name. We would like to verify on the first fragment, using their email. Possibly even their NCC ID as well. Name is way too common.
- Styling - We figure it'd be easy to create "styles" to use to unify the UI. This shouldn't effect DB team, but wanted to include it.
I'm probably missing some stuff, so UI team feel free to fill in anything I missed.
Current Behavior
Coming from issue #94 (closed) , a lot of the original plans for this were in issues #139 (closed), #140 (closed), #142 (closed), #143 (closed), #154 (closed), #155 (closed) and #157 (closed). They'll probably need to be updated to start.
Benefits (Why is it necessary?)
Certain key elements we should be on the same page with are going to be things like column / variable names, what each fragment does, expected behaviors, etc. Should take this opportunity to get on the same page now and use the discord for discussion in between.