How web-fda-neu/ai66b--g6--topic-b2--pitch-reservation-management works
Pitch Point is a football-pitch discovery and booking web application, but the sampled implementation is an early-stage prototype: search and featured listings use in-browser sample data, while the API provides generic item CRUD and account authentication. The visible customer flow is home/search → pitch listings → pitch detail; registration/login provides a token-backed session. README capabilities such as bookings, payments, reviews, operator management, statistics, notifications, and role-based administration are documented future/product scope, but no corresponding runtime modules appear in the supplied tree. Frontend page wiring is based on the tree and excerpts; unsampled routes are represented only where paths are certain.
Main entry points: auth.py Authentication routes · api.js API client · deps.py Identity dependency · database.py SQL database
Components 17
Pitch discovery
- Home and featured pitches
frontend/js/pages/home.js - Pitch search
frontend/js/pages/search.js - Sample pitch data
frontend/js/data/pitches.js - Pitch detail page
frontend/js/pages/pitch-detail.js
Accounts
- Registration page
frontend/js/pages/register.js - Login page
frontend/js/pages/login.js - Session and header state
frontend/js/auth.js
Backend API
- API client
frontend/js/api.js - API application
backend/main.py - Authentication routes
backend/routers/auth.py - Item routes
backend/routers/items.py
Persistence and security
- Identity dependency
backend/deps.py - Password and JWT
backend/security.py - User and item models
backend/models.py - SQL database
backend/database.py
Other components
- Customer
- API service
Connections 22
- Customer → Home and featured pitches: opens
- Customer → Pitch search: searches
- Customer → Registration page: registers
- Customer → Login page: signs in
- Home and featured pitches → Sample pitch data: renders samples
- Pitch search → Sample pitch data: filters samples
- Pitch search → Pitch detail page: opens pitch
- Registration page → API client: registers via
- Login page → API client: authenticates via
- API client → Session and header state: reads token
- API client → API service: HTTP requests
- API service → API application: serves
- API application → Authentication routes: dispatches
- API application → Item routes: dispatches
- Authentication routes → SQL database: reads/writes users
- Authentication routes → Password and JWT: hashes and issues tokens
- Authentication routes → Identity dependency: uses identity
- Item routes → SQL database: reads/writes items
- Item routes → Identity dependency: checks current user
- Identity dependency → Password and JWT: decodes token
- Identity dependency → SQL database: loads user
- SQL database → User and item models: maps records