How shiross00/swp391_su25 works
Project type and purpose
• This is a full-stack “Blood Donation Support System” comprising a React+TypeScript front-end and a Java Spring Boot back-end.
• Purpose: manage donation events, registrations, donor profiles, blood requests/stock, health checks, notifications, blogs and achievements.
File structure
A. Top-level layout
• back-end/…/blood-donation-support-system: Spring Boot service
• front-end/: Vite-powered React application
B. back-end module
• pom.xml, Dockerfile, application.properties – build & config
• src/main/java/com/swp391/superapp/bloodsupport
– controller: REST API endpoints (EventAPI, etc.)
– entity: JPA domain models (Account, BloodDonationEvent, DonationRegistration, etc.)
– repository: Spring Data JPA interfaces for persistence
– service: business logic & email sender
– infra: JPA utility
• src/main/resources: application and meta-inf configs
C. front-end module
• package.json, tsconfig, tailwind.config.js, vite.config.ts – build & lint config
• public/index.html – single-page host
• src/
– App.tsx, main.tsx – entry points
– components/ (header, footer, button)
– pages/home.tsx – views
– utils/constants.tsx, types.ts – shared types & constants
– assets/ – images/styles
README insights
• Only placeholder title; no architecture details. Rely on file structure for patterns.