How cepdnaclk/e19-co227-engineering-education-unit works
Project type and purpose
• This is a full-stack web application (“Engineering Education Unit”) consisting of:
– A React-based SPA in Application/FrontEnd/navbar
– A Java Spring Boot backend in Application/BackEnd/General_Elective_Subjects
– A MySQL schema (eeu.sql) under Application/Database
• Purpose: allow Admin, Lecturers and Students to browse courses, book rooms, view staff details, manage resources, and secure operations via JWT.
File structure
• Top-level “Application” folder separates FrontEnd, BackEnd, and Database artifacts.
• BackEnd is a monolith using Spring Boot’s standard package layering:
– auth (AuthenticationController, JWT filter, services)
– Config (CORS, security, beans)
– Controller (REST endpoints: GES, Staff, File upload, Seminar)
– Service (+Impl) (business logic)
– Repository (Spring Data JPA interfaces)
– Model (JPA entities: User, Role, GES, Staff, Token, etc.)
– resources (application.properties, static JSON/text)
• FrontEnd is a React project with:
– src/Pages (per-feature page components)
– src/components (UI pieces: Navbar, AppBar, Footer, Search, ImageSlider)
– RoutesConfig for client-side routing
• Database: single SQL file to instantiate MySQL schema.
README for additional insights
• Technology stack: React + Bootstrap, Java/Spring, Spring Security with JWT, MySQL.
• Roles: Admin (content management, override bookings, upload videos), Users (booking, browse resources).
Key details not to omit
– AuthenticationController and JwtAuthenticationFilter as the security gateway
– Repositories connecting to MySQL (show table/entity examples)
– File upload/download path
– CORS configuration enabling UI↔API cross-origin calls
– Any external dependencies (e.g., SMTP if email verification is later added)