kannan-a7801/schoolwebsite

Purpose and deployable surfaces

This is a school LMS repository with a Java/Spring backend, a lightweight learner-facing static frontend, a separate React admin portal, and versioned curriculum documents for grades 3–10. The primary runtime entry points are backend/src/main/java/com/school/lms/LmsApplication.java, frontend/index.html, frontend/app.js, and admin-portal/src/index.js.

Backend API and application layering

The backend is a Spring Boot 3 application organized as REST controller → service → JPA repository → relational database. Controllers expose role-oriented API surfaces for authentication, courses, students, teachers, and administration:

• backend/src/main/java/com/school/lms/controller/AuthController.java

• backend/src/main/java/com/school/lms/controller/CourseController.java

• backend/src/main/java/com/school/lms/controller/AdminController.java

Business logic is separated by domain in backend/src/main/java/com/school/lms/service/StudentService.java, backend/src/main/java/com/school/lms/service/TeacherService.java, and backend/src/main/java/com/school/lms/service/CourseService.java. Error translation is centralized at backend/src/main/java/com/school/lms/exception/GlobalExceptionHandler.java.

Identity and authorization boundary

Authentication is JWT-based. Login/signup requests enter through the auth controller and service, then JWT issuance/validation and request authentication are handled by the security package. Role data exists as a persisted domain concept, supporting admin, teacher, and student-specific API behavior.

• backend/src/main/java/com/school/lms/security/SecurityConfig.java

• backend/src/main/java/com/school/lms/security/JwtAuthenticationFilter.java

• backend/src/main/java/com/school/lms/security/JwtUtils.java

The frontend/admin clients are expected to cross this boundary through authenticated HTTP requests rather than direct database access.

Learning and school operations domain

The persistent model covers course hierarchy and classroom activity: terms and chapters define curriculum, day classes and attendance capture delivery, and progress, quizzes, submissions, grades, and daily reports capture student work and evaluation.

• backend/src/main/java/com/school/lms/entity/Term.java

• backend/src/main/java/com/school/lms/entity/Chapter.java

• backend/src/main/java/com/school/lms/entity/StudentProgress.java

Related operational flows include quiz submission/results, teacher daily reporting, submission review, and administrative dashboard aggregation, represented by DTO contracts such as backend/src/main/java/com/school/lms/dto/QuizSubmissionDto.java, backend/src/main/java/com/school/lms/dto/DailyReportDto.java, and backend/src/main/java/com/school/lms/dto/AdminDashboardStatsDto.java.

Client applications

The learner-facing client is plain browser JavaScript, with course content/data separated from rendering logic:

• frontend/index.html

• frontend/app.js

• frontend/coursesData.js

The admin portal is a separate React application. admin-portal/src/App.js is its composition point; layout/navigation is shared through admin-portal/src/components/layout/AdminLayout.js; global auth state and API access are isolated in admin-portal/src/context/AuthContext.js and admin-portal/src/services/api.js. Its pages cover students, courses, approvals, submissions, analytics, and system administration.

Data, infrastructure, and external services

The backend uses Spring Data JPA/Hibernate with MySQL connectivity and HikariCP, configured through backend/src/main/resources/application.yml; repositories define database access boundaries, e.g. backend/src/main/java/com/school/lms/repository/UserRepository.java and backend/src/main/java/com/school/lms/repository/SubmissionRepository.java. It also includes backend/src/main/java/com/school/lms/service/SupabaseStorageService.java, indicating Supabase-backed object storage for uploaded/content files.

Curriculum source material is filesystem-managed rather than modeled solely in code. It is organized by grade, chapter, class session, assets, activities, and assessments under paths such as asset/6th class/Chapter 2 Digital Technologies, asset/8th class/Chapter 3 Coding Fundamentals, and asset/10th class/chapter 1. This document corpus is a major content boundary: ingestion, normalization, and storage mapping would need to accommodate inconsistent directory/file naming and mixed DOCX/PDF formats.