mervin0266/iqac-plateform

1. Purpose and entry points

IQAC Platform is a two-process institutional-quality-management application: a React/Vite frontend for public and authenticated administration views, plus an Express backend for persistent operational data. Frontend starts at src/main.tsx and composes the application in src/app/App.tsx; backend starts at src/app/backend/server.js.

2. Frontend application shell

src/app/App.tsx is the primary UI composition and navigation boundary. It brings together public-site presentation, login, dashboard, and content-management pages. Shared authenticated layout/navigation is represented by src/app/components/Header.tsx, src/app/components/Sidebar.tsx, and src/app/components/DashboardPage.tsx.

3. Public versus administrative experiences

The UI separates public institutional content from managed IQAC workflows. Public-facing rendering is centered on src/app/components/PublicWebsite.tsx, src/app/components/PublicHomePage.tsx, and src/app/components/PublicNavBar.tsx. Administrative pages cover departments, faculty, students, documents, achievements, strategic plans, and placement/research areas, such as src/app/components/DepartmentTrackingPage.tsx, src/app/components/AchievementsPage.tsx, and src/app/components/StrategicPlanPage.tsx.

4. Authentication and authorization boundary

Frontend authentication state is owned by src/app/contexts/AuthContext.tsx. UI-level access enforcement uses src/app/components/PermissionGuard.tsx and the permission definitions in src/app/config/permissions.ts. Backend requests cross the trust boundary through src/app/backend/middleware/auth.js; authorization and audit behavior should remain server-enforced rather than relying on the UI guard.

5. Backend API and domain modules

The Express server mounts resource-specific route modules from src/app/backend/routes/, which dispatch to controllers in src/app/backend/controllers/. Key domain slices include identity (src/app/backend/routes/auth.js, src/app/backend/controllers/authController.js, src/app/backend/models/User.js), institutional entities (src/app/backend/routes/departments.js, src/app/backend/controllers/departmentController.js, src/app/backend/models/Department.js), and document governance (src/app/backend/routes/documents.js, src/app/backend/controllers/documentController.js, src/app/backend/models/Document.js).

6. Persistence, workflow, and observability

Database configuration is isolated in src/app/backend/config/database.js, while model registration is consolidated in src/app/backend/models/index.js. The backend supports governance workflows beyond CRUD: edit-request lifecycle through src/app/backend/models/EditRequest.js and src/app/backend/controllers/editRequestController.js; user notifications through src/app/backend/models/Notification.js and src/app/backend/middleware/notificationHelper.js; and audit capture through src/app/backend/models/AuditLog.js and src/app/backend/middleware/auditLogger.js. Seeding/initialization is provided by src/app/backend/config/autoSeed.js and src/app/backend/scripts/initDatabase.js.

7. Runtime and delivery shape

The frontend runs under Vite, configured by vite.config.ts, with TypeScript/React source under src/ and static host entry index.html. The backend is a separately installed Node.js package under src/app/backend/package.json, run independently from the frontend. The repository includes backend deployment and operational guidance at src/app/backend/DEPLOYMENT.md and src/app/backend/QUICKSTART.md; a hosted design/site reference is identified in README.md.