How abdallah116294/edulink works
Project type and purpose
• EduLink is a backend‐focused, full-stack educational management system built as an ASP.NET Core Web API following Clean Architecture.
• It provides REST endpoints for user management, student/staff operations, academic processes (classes, subjects, exams, grades, attendance), and financial management (fees).
File structure
• Top-level solution (EduLink.API.sln) spans five main projects:
• EduLink.API (Presentation / Web API)
• EduLink.Core (Domain)
• EduLink.Repository (Data Access)
• EduLink.Service (Business Logic)
• EduLink.Utilities (DTOs & Helpers)
• Edulink.Tests (Testing)
• Patterns:
• Controllers → call Services (in Service layer)
• Services → orchestrate Repositories via IUnitOfWork / Repositories (in Repository layer)
• Repositories → use EF Core DbContext → SQL Server
• Domain Entities live in Core; DTOs in Utilities
• Specifications encapsulate query logic
• AutoMapper profiles (MappingProfile) used to map Entities↔DTOs
• Extensions bootstrap DI, Swagger, Configuration
README for additional insights
• Design patterns: Repository, Unit of Work, Specification, Dependency Injection, CQRS
• Technology stack: ASP.NET Core 8.0, EF Core, SQL Server, ASP.NET Identity, Swagger, XUnit, Serilog, FluentValidation
Elements
• Rectangles for components