You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,14 @@ Create a single source of truth for operational data that keeps the team synchro
9
9
- Operations planning for seasons, events, innhopps, manifests, and landing zones.
10
10
- Participant roster and event assignments, including crew roles per manifest.
11
11
- Logistics tracking for transports, vehicles, accommodations, meals, and ad-hoc logistics items.
12
+
- Registration backbone for participant-event lifecycle tracking, payment obligations, and activity history.
12
13
- Safety and compliance fields on events/innhopps (NOTAM, risk assessment, safety precautions).
13
14
- RBAC-backed login sessions (OIDC) with seeded roles for core operational duties.
14
15
15
16
## Not yet implemented
16
-
- Payments, waivers, certifications, and health declarations.
17
-
- Automated notifications, check-in flows, or public driver route pages.
17
+
- Public registration pages, automated notifications, and campaign email sending.
18
+
- Payment provider integrations, waivers, certifications, and health declarations.
19
+
- Check-in flows or public driver route pages.
18
20
- Analytics dashboards beyond raw data access.
19
21
20
22
## User roles
@@ -34,13 +36,14 @@ RBAC ensures each user only sees the modules and actions needed for their duties
34
36
35
37
## Workflows
36
38
1.**Event planning**: Create seasons/events, define innhopps with landing and safety details, and publish manifests.
37
-
2.**Participant coordination**: Maintain the roster, attach participants to events, and assign crew roles per manifest.
39
+
2.**Participant coordination**: Maintain the roster, attach participants to events, assign crew roles per manifest, and track registrations with status, notes, and payment records.
38
40
3.**Logistics tracking**: Capture transports, vehicles, accommodations, meals, and other logistics items per event.
39
41
40
42
## What you can do today
41
43
- Build seasons and events, including detailed innhopp plans with landing areas, NOTAM notes, risk mitigation, and hospital/boat coverage metadata.
42
44
- Register airfields, attach them to events, and manage manifests with capacity, staff slots, and participant assignments.
43
45
- Maintain a participant roster (roles, experience, contacts), add people to events/manifests, and track crew roles such as Jump Master/Leader, Ground Crew, Driver, and Packer.
46
+
- Create event registrations for participants, record deposit/balance payment entries, track registration status, and append internal activity notes.
44
47
- Coordinate transports, vehicles, accommodations, meals, and other logistics items per operation.
45
48
- Authenticate via OIDC (authorization code flow), persist sessions in secure cookies, and enforce role-based permissions seeded on startup (Admin, Staff, Jump Master, Jump Leader, Ground Crew, Driver, Packer, Participant). Set `DEV_ALLOW_ALL=true` to bypass auth locally.
46
49
- Use the frontend pages for login, events, manifests, participants, logistics, seasons, innhopp details, and airfield details (see `frontend/src/pages/` and `frontend/src/components/Layout.tsx` for the routes).
|`VITE_GOOGLE_MAPS_API_KEY`| Google Maps API key for route duration features | placeholder value |
110
113
111
114
## API and UI references
112
-
- Backend endpoints for seasons, events, innhopps, manifests, airfields, participants, crew assignments, logistics transports, and auth are documented in `backend/README.md`.
115
+
- Backend endpoints for seasons, events, innhopps, manifests, airfields, participants, registrations, crew assignments, logistics transports, and auth are documented in `backend/README.md`.
113
116
- Frontend routes include `/login`, `/events`, `/events/:eventId`, `/events/:eventId/innhopps/:innhoppId`, `/manifests`, `/manifests/:manifestId`, `/participants`, `/participants/:participantId`, `/logistics`, `/airfields/:airfieldId`, plus creation flows for seasons, events, manifests, and participants.
0 commit comments