Skip to content

School Result Management

Rebuilt a plain-PHP student result project in Laravel 13: 26 models, 30 migrations, 28 controllers, 7 services for grading, score sheets, report cards, and result PINs, and 33 tests.

How it’s built

How it’s built

School Result Management · Laravel 13 school result system rebuilt from a legacy PHP project

I forked a plain-PHP student result project, moved it into legacy/, and rebuilt it in Laravel 13 across 5 commits: 26 Eloquent models, 30 migrations, 28 controllers, 7 domain services for grading, score sheets, report cards and result-checker PINs, and 33 tests. Teachers enter scores on validated sheets and admins issue printable PIN batches.

commits by me (~22,100 lines added)
5
Eloquent models / migrations
26 / 30
controllers
28
domain services
7
test cases (19 in SchoolWorkflowTest)
33

Technology and what it does here

Laravel 13 (PHP 8.3)
Routing, Eloquent models, migrations, Blade views and auth
Blade
67 view files for score entry, results, PIN management and printing
PHPUnit
Feature tests for auth flows and the end-to-end school workflow
Tailwind CSS + Vite
Frontend styling and asset build
Database seeders
AcademicStructure, Curriculum and DemoSchool seeders for guardians, subjects and settings
Artisan command
RepairSubjectRegistrations fixes student subject registrations

Implementation details

  • ResultPinService generates PIN batches inside a DB transaction with serials like 'GPP-yy-NNNNNN', random_int PINs, max_uses and expires_at.
  • The original upstream PHP pages and SQL dump are preserved under legacy/ while the Laravel app replaces them.
  • web.php defines 96 Route:: declarations.

Technologies

  • Laravel
  • Migration
  • School Records

Next project · AI/ML Engineer

Sigmant

Portfolio assistant

Gabriel’s projects, experience, and research