EN FR
All projects

PFE · Full-stack product engineering

École Platform — Trilingual School ERP/LMS

A trilingual school platform connecting administration, teaching, learning and billing across web and mobile clients.

École Platform — Trilingual School ERP/LMS product overview
Feb. - June 2026Full-stack Developer

01

The problem

K-12 schools need one coherent workflow for enrolment, classes, learning content, attendance, grades, communication and billing instead of disconnected tools and repeated data entry.

Constraints

  • Arabic, French and English interfaces, including RTL behavior.
  • Different permissions and workflows for administrators, teachers, pupils and parents.
  • Web and mobile clients sharing one API while remaining independently deployable.

02

My contribution

03

Technical decisions

01

Shared API, purpose-built clients

FastAPI centralizes domain rules while React serves administration and teaching and Flutter serves pupil and parent workflows.

Trade-off: More client code to maintain, in exchange for interfaces adapted to each role and device.

02

Operational features as product features

Object scanning, telemetry, containerization and Helm delivery are treated as part of the system rather than an afterthought.

Trade-off: A wider system surface, balanced by reproducible environments and clearer operating boundaries.

04

Verifiable outcomes

  1. A repository-backed trilingual ERP/LMS/billing implementation spanning backend, web and mobile.
  2. Automated backend, web, end-to-end and contract testing is part of the delivery workflow.
  3. The project ran from February through June 2026; the PFE internship continued through July 2026.

05

Product evidence

Administration dashboard
Application screenshot embedded in the PFE report and extracted without redesign. It shows demonstration data from the project prototype.Report extractDemo modeCaptured: Source commit: bdcaa912
01Seeded demo data

Administration dashboard

Application screenshot embedded in the PFE report and extracted without redesign. It shows demonstration data from the project prototype.

Class workflow
Full-resolution product screenshot extracted from the PFE report, showing the implemented class context rather than a portfolio mockup.Report extractDemo modeCaptured: Source commit: bdcaa912
02Seeded demo data

Class workflow

Full-resolution product screenshot extracted from the PFE report, showing the implemented class context rather than a portfolio mockup.

Billing workflow
Invoice-management screen extracted from the PFE report. Values belong to the documented prototype demonstration.Report extractDemo modeCaptured: Source commit: bdcaa912
03Seeded demo data

Billing workflow

Invoice-management screen extracted from the PFE report. Values belong to the documented prototype demonstration.

06

What I learned

  • Role-specific workflows must be designed as one domain, not as separate screens.
  • Internationalization affects navigation, documents and data modeling—not only translated labels.

07

What I would change

  • Start with a narrower operational pilot before expanding every school module.
  • Build the evidence-capture workflow into each release so product media stays current.
Next projectAPM Observability — Multi-tenant OTel Platform