Monster Basket web app / back end for sport activities

The goal of this project is to have a digital platform where members, with different types of roles, can read and write information about all services that Monster Basket proposes. Monster Basket is a (small) sport school where kids (= type of member), once a week, between 5 and 12 years can train basketball -and psychomotor skills. Monster Basket is a non-profit organisation, and there members does not play in a competition. Core functionalities: - The user tier is 50 and the main focus of the web app is communication. We want to avoid communication with our members through WhatsApp and emails. Communication can be send through the web app to one, a group of members or all members with a specific role. - The different roles are: admin, staff, parent and kid. - Members can be managed in the web app (CRUD). Personal information can be stored by admin or staff, and a part of the information can be read by one or more members (of type parent). A parent can be linked with more than one members of type parent. - Members of type kid can be managed per season (CRUD) (ex. 2024-2025, 2025-2026, …), and a season contains about 34 sessions. Each saterday morning there are two sessions (psychomotor skills and basketball with each his specific exercices). - Per session (CRUD) a member (of type staff) can manage the members who are present. A member of type staff will need a grid view where he can, per session, easily add information like presents and feedback per member. - A staff member can manage his exercices (CRUD) (there are different type of exercices according to age and type of skills). Exercices can be linked to sessions. - A staff member can manage feedback per member and choose which feedback/information can be shared with the parent(s) (= type of member). - An admin or a staff member can invite a member (parent/kid) to join the pweb app. A member can login/logoff through email and MFA. - A member of type parent will have, after login, all relavant communication (personally or by group). He/she will be able to reply (private/public by group). If there is an outstanding debt, it must be shown (with due date) onnthe manding page wit all relavant information/communication. - Every season the parent(s) need to pay a fee. Paiement doesn’t need to be managed by the web app, but an overview of the payment history is needed per season. Paiements will be added manually by the admin. - The admin need to be able to manage events. An event can be a 1 day team building or an internship of a week. Parents need to be able to register for an event. - A staff member need to be able to manage kids with there presents, global and session feedback, communicate with parents and manage their exercices (préparation and adjustments during the sessions). - The user interface needs to be multilanguage. At the beginning all the user interface will be in French. All translations will be provided. - In a later phase the staff module must be extended and a few articles (like t-shirts) must be online offered at a fix price. - The web app must be integrated or overlap with the website ([login to view URL]). - I have basic programming skills (a lot of years ago) so transfer knowledge and support after go live are important for me.