2.1 KiB
2.1 KiB
Core Features:
-
Attendance Table
- A table with:
- Rows: Each game date (in DD/MM/YY format).
- Columns: Each player’s name (8 fixed names) and one column for a guest (labeled “Guest” or “Mystery”).
- Each cell (except for the date) is clickable to mark attendance (“Yes” or blank).
- The user should be able to adapt the name of the players.
- A table with:
-
Add/Edit Dates
- Ability to add a new date (row) to the table.
-
Mark Attendance
- Clicking a cell toggles attendance for that player/guest on that date.
- “Yes” means attending; blank means not attending.
- The user should be able to adapt the name of the guest.
- The user should be able to adapt the name of the players.
- The user should be able only to choose from Yes or blank to mark attendance.
-
Data Persistence
- The table’s state (who is attending which date) is saved and loaded automatically (from a JSON file).
- No login or authentication needed (handled by your reverse proxy).
-
Guest/Mystery Player
- The last column is always for a guest. You can leave the name as “Guest” or allow it to be edited per date.
What you don’t need for MVP:
- User registration, login, or roles.
- Notifications, reminders, or analytics.
- Player management (names are fixed).
- Complex UI-just a simple table.
How it works (user flow):
- User opens the web app.
- Sees a table with upcoming dates and player names.
- Clicks on their name under a date to mark themselves as attending (“Yes”).
- Guest attendance can also be marked.
- Data is saved automatically.
Technical outline:
- Frontend: Simple HTML table, checkboxes or clickable cells, minimal CSS.
- Backend: JSON file for storing attendance.
- No authentication logic needed (handled at the proxy level).
Summary:
You only need a simple, editable attendance table with dates as rows and player names (plus guest) as columns. Users can mark their attendance with a click. No login, no user management, just a fast and easy attendance tracker.