Repository navigation
Deliverable 2
Role: Registered Participant
- What: The main content group displays match metadata and the list of registered participants.
- Where: Information is structured in a centered Bootstrap card, with the participant roster located directly below the match details.
- How: The user interacts via a green primary "Confirm attendance" button. Upon clicking, the system dynamically updates their status to "Attendance confirmed" in the list below without requiring a full page reload.
Role: Match Organizer
- What: A destructive action flow and a confirmation modal overlay.
- Where: The "Cancel match" button is located in the action area of the match details. The confirmation prompt is a centered modal overlaying the main interface.
- How: The organizer triggers the flow using a red outline button. To prevent accidental deletions, a modal requires explicit confirmation before processing the cancellation and notifying participants.
Role: Standard Player
- What: A capacity warning and the waiting list enrollment action.
- Where: Located within the main match details card, replacing the standard "Join match" action when capacity is at 100%.
- How: The user receives a clear visual warning that the match is full. By clicking the blue "Join waiting list" button, the system registers the request and displays inline green feedback showing their exact queue position.
Role: Waitlisted Player / System View
- What: Participant rosters split into active players and the waiting list, alongside system status alerts.
- Where: Structured as two distinct list groups below the main match data. System feedback is displayed as an alert banner at the top of the interface.
- How: When a confirmed player leaves, the system automatically assigns the slot to position #1. The interface reflects this via a blue informational banner and a status update in the participant list, ensuring the process is transparent.
Role: Any Logged-in User
- What: Filtering parameters (Date, Location, Skill level) and the catalog of available matches.
- Where: The filter block is positioned at the top of the view for immediate access, with the resulting match cards displayed in a responsive grid below.
- How: Users define parameters using dropdown selectors and execute the search via the "Apply filters" button. The grid dynamically updates to show matches matching the criteria. If no matches match the criteria, a clean empty state message is rendered.
https://github.com/[scanonc/Local-Sports](https://github.com/scanonc/Local-Sports)
main.
feature/name, fix/name
is required 1 review by the Scrum Master
- Continue using GitHub branches and pull requests to organize and review changes.
- Continue dividing the requirements among team members to work in parallel.
- Continue testing implemented functionalities before integrating them into the main branch.
- Start conducting short team reviews of completed functionalities before merging them.
- Start tracking the progress of each requirement more consistently during the sprint.
- Stop relying only on individual testing before merging changes.
- Stop leaving integration and testing until the end of the sprint.