How guillerg01/phase_system_admin works
Project type and purpose
• This is a Next.js (v13+) full‑stack web application (front‑end focused) that exposes two main sections:
• A public “landing” area with basic marketing pages
• An authenticated “admin” dashboard (drivers, payments, reservations, tariffs)
• The UI fetches and displays data via REST‑style API services (ApiClientService and specific EntityApiServices)
File structure
• Top‑level Next.js files: next.config.ts, tsconfig.json, postcss.config.mjs
• “public” folder holds static assets for landing pages
• “src/app” implements Next.js App Router with two route segments:
• (landing) – unauthenticated marketing pages
• admin – protected dashboard pages
• “src/components”: reusable React components by feature (Auth, LandingPage, admin subfolders, generic tables, modals, buttons, etc.)
• “src/context”: React Context providers (AuthContext, selected‑items)
• “src/hooks”: custom hooks for data fetching and table state
• “src/services”: abstraction over REST API calls (ApiClientService, DriverApiServices, etc.)
• “src/utils”: shared utilities (formatters, pdf generator, toastify, loading spinners)
README
• Confirms Next.js scaffold via create‑next‑app
• Mentions frontend optimizations (next/font) and Vercel deployment
• No backend code; all API surfaces are consumed remotely
Detail without over‑splitting
• Related components (e.g., all “admin/*” components under one cluster)
• Cross‑cutting concerns (authentication, global utils)