How team-pepe/pepe-constructor- works
Project type and purpose
• This is a full‑stack web application for managing construction works: user/role management, attendance (with geolocation), material requests, work‑zone tasks, and payment/report generation.
• Frontend: React + Vite + Tailwind + Radix UI + Leaflet/Turf.
• Backend: Node.js + Express + Prisma + PostgreSQL + JWT + PDFKit + Chart.js.
File structure
• Top‐level directories:
• backend/ — Express server, Prisma schema, migrations, controllers, routes, middleware, config, utilities
• frontend/ — Vite‐powered React app, global styles, UI components, page components, feature modules, services, hooks
• Configuration and build files:
• backend/.env‑example, package.json, prisma/schema.prisma, prisma/migrations
• frontend/.env.example, vite.config.js, tailwind.config.js, package.json
• Patterns:
• Backend follows MVC‑style separation (routes → controllers → utils/config)
• Frontend follows component‑based organization with feature folders, shared UI library, context/hooks
README for additional insights
• Modules: User/auth, attendance, materials, work zones/tasks, dashboard/reporting
• Goals: real‑time geolocation, PDF/chart generation, role‑based access, offline sync (future)
Detail but keep clarity
• Backend route group mapping to its controller and utility set
• Prisma schema as part of the Data layer, showing entities if desired
• Don’t overpopulate with every file—focus on logical modules and their interactions