We would want possible participants to register themselves into events of their choices, that is available in our website. Not all events will have the registration flow. Like GNOME Asia event mustn't have registration flow in our website, but for events like Gnome hackathon must have registration flow.
Make sure total participants must be less than max capacity of event.
Implement model for event participant
First Name
Last Name
Email
Academy
Phone
Age group
Add other relevant columns
Event and users will have many-to-many relationships.
View(s):
Registration entries: Only admin can see this
Registration backend: As a form but in backend views
Admin Panel: export as CSV file
Validation(s)
total participants =< Max capacity
Flow(s)
Post registration flow
Pre registration requirements collection [Might move this away]
For event 1, we might ask user for discord name, LinkedIn URL, name but not phone number.
For event w, we might ask user for LinkedIn URL, name, and phone number.
We would want possible participants to register themselves into events of their choices, that is available in our website. Not all events will have the registration flow. Like
GNOME Asia eventmustn't have registration flow in our website, but for events likeGnome hackathonmust have registration flow.Make sure total participants must be less than max capacity of event.
Implement model for event participant
Add other relevant columns
Event and users will have many-to-many relationships.
View(s):
Validation(s)
Flow(s)
Post registration flow
Pre registration requirements collection [Might move this away]