How ngocanhit201/dpo works
Project type and purpose
• This is a full-stack web application for managing school administrative procedures.
• Frontend: React + Next.js + MUI + Tailwind CSS
• Backend: C# ASP.NET Core 8 with JWT authentication and EF Core for SQL Server
• Purpose: Allow students to view and submit procedure requests, and allow faculty/staff to review, approve, or reject them, with file uploads and tracking of workflow.
File structure
• Top-level directories:
• DPO_FE – the Next.js React UI
• DPO_BE – the ASP.NET Core Web API / MVC backend
• FE patterns:
• src/app – Next.js “app router” pages & layouts (blank and main layouts for student/teacher)
• src/components, @core, @menu, @layouts – UI component libraries & themes
• src/api – client-side API calls (Axios wrappers)
• BE patterns:
• Controllers (AuthController, CasesController, etc.) implementing REST endpoints
• Areas/Files – MVC area for file management using elFinder
• Models + DbContext (StudentProceduresOnlineContext) using EF Core
• Mapper folder with DTOs & AutoMapper profiles
• Utils (mail settings, constants)
• appsettings.json – configuration for DB, JWT, SMTP
• wwwroot/Uploads – static file store for attachments
• Deployment/config:
• DPO_FE/.env.example, next.config.mjs – frontend environment & build
• DPO_BE/Program.cs, launchSettings.json – backend startup & launch profiles
Key README insights
• Describes two user flows: student side and staff side
• Emphasizes JWT auth, file attachments, workflow tracking, SQL Server