Overview
A single system that combines a school's back-office management system with its public website. Day-to-day content is editable at runtime by staff with the right permission, with no code changes or redeploys, and the site is installable as a PWA with a light and dark theme.
Problem
A school needs back-office records, admissions, fees and a public website, and wants non-technical staff to keep the content up to date themselves.
Solution
A modular system where permissions control who can change what: school records and academics, online admissions that provision parent and student portals automatically, fees and billing, and a block-based page builder for the website.
Engineering Case Study
Approach: Delivered in phases: identity and permissions, school records and the website CMS, then attendance, timetable, gradebook and report cards, online admissions, student-management depth, reports and inventory, fees and billing, and finally the page builder.
Architecture: A modular monolith in Clean Architecture (Domain, Application, Infrastructure, Web) on ASP.NET Core MVC with EF Core and SQL Server. Admin, Parent and Student areas share one permission-based authorization framework, with unit tests and integration tests that make real HTTP requests against the app.
Features: Attendance, timetable, gradebook and report cards; online admissions with automatic portal provisioning; Form 1 to 6 structure with ZIMSEC and Cambridge curriculum tagging and O-Level and A-Level grading; fees, invoices and a Bursar role; printable ID cards; on-demand good-conduct, attendance, enrolment and transcript letters; inventory and asset management; multi-provider email with failover.
Outcome: Phases 1 to 3 and the student-management, curriculum, reporting, billing and page-builder expansions are built.