How nguyen-anh-hao/hhkt-ex-tkpm works
Project type and purpose
• This is a full‑stack student‑management system comprising:
• A Next.js (React) single‑page application for class, course, student, registration, transcript management.
• A Java Spring Boot REST API backend implementing layered MVC (controllers, services, repositories) with import/export, validation, and database persistence.
• A relational database (seeded via Docker) storing domain entities (Student, Course, ClassRegistration, etc.).
File structure
• Top‑level directories:
• client/: Next.js frontend
• server/: Spring Boot backend + Docker Compose + SQL scripts
• docs/: project guides
• Frontend pattern:
• src/app: route directories (class‑management, course‑management, …) each with page.tsx, components, actions
• src/libs: API wrappers, React Query hooks, service facades, Zustand stores, validators, utils
• Backend pattern:
• src/main/java/org/example/backend/config: CORS, Jackson, OpenAPI, status‑rules configuration
• controller → service (including import/export factories) → repository → domain
• dto (request/response) + mappers to translate domain ↔ DTO
• resources: application.yml, SQL seeds, import/export config
README for additional insights
• Use cases: Manage students, courses, classes, registrations, reference data, status‑rules, transcripts.
Essential architectural elements to capture
• All frontend feature modules (class‑management, student‑management, etc.)
• API client layer (libs/api) and React Query hooks (libs/hooks)
• Backend import/export & validation factories
• DTO ↔ Entity mapping layer
• Database schema (seed scripts)
• Docker‑Compose orchestration for DB