Architecture / Full-Stack

EduTrack — Attendance Management for a School Platform (EtudiaLab)

EduTrack is the attendance-management module of EtudiaLab's school platform. During my internship I was responsible for the whole technical side of the prototype: the architecture and data model, the draw.io diagrams and Figma mockups, the Django REST API and the React interfaces for teachers, students, parents and school administrators.

Role
Technical architect and sole full-stack developer
Context
8-week internship at EtudiaLab, a Moroccan EdTech startup
Period
05/2026 – 07/2026

Screenshots & diagrams

Captured from the running project. Click to view full screen.

Use cases (UML): 17 use cases across teachers, students, parents, school admins and EtudiaLab admins.
Class diagram: users, schools, timetable, attendance, justifications, notifications and parent accounts.
Lifecycle of an attendance record: not recorded → present / late / absent → justified or refused.
Deployment: React + Vite front end, Django REST API and PostgreSQL as three Docker Compose services.
Data flows (DFD level 1) between teachers, students, parents, the school admin and the data stores.
Decision analysis for the meetings feature: 4 options compared on effort, data ownership and Docker compatibility, with a recommendation for the prototype and for production.

The problem

EtudiaLab needed a working prototype of its school-management platform, with absence management at its core: teachers record attendance, parents are alerted, absences get justified, and the school sees which students are at risk.

The solution

I designed the architecture and built the prototype alone: three role-based React apps (school, teacher, admin) plus a mobile app for students and parents, on a Django REST back end of 13 apps, 16 data models and 20+ endpoints, all started with one Docker Compose command.

The impact

Delivered in 8 weekly sprints: 7 EduTrack screens taken from Figma mockups to working code, with weekly progress reports to my supervisor. Defended before the ENSIASD jury on 12 November 2026 (PFA) and passed.

What I did

  1. 01

    Designed the architecture first (week 1): entity-relationship model, API contract, UML diagrams (use case, class, sequence, activity, state, deployment, data flow) in draw.io and 7 screens in Figma with a small design system.

  2. 02

    Compared four ways to add video meetings (external link, Zoom / Google Meet API, in-house WebRTC, WebSockets) on effort, data ownership and deployment, and recommended one option for the prototype and one for production.

  3. 03

    Worked spec-first with GitHub Spec Kit: each feature went from a written specification to a technical plan and a task list before AI-assisted implementation, so the specs stayed the source of truth.

  4. 04

    Built the back end with Django REST Framework: 13 Django apps and 16 models, JWT authentication with role-based permissions, and 20+ REST endpoints tested with Postman.

  5. 05

    Built the teacher side: a dashboard with daily sessions and alerts, an attendance sheet (present / absent / late, with each student's running absence count) and a weekly class report with PDF and CSV export.

  6. 06

    Built the student and parent mobile app: attendance history, alerts, and a 4-step wizard to justify an absence with a reason and an uploaded document, which the teacher then approves or rejects.

  7. 07

    Built the school-admin view: attendance by class, at-risk students and one-click notification of their parents.

  8. 08

    Automated notifications with Django signals, so recording an absence or reviewing a justification notifies the right people without coupling the modules.

  9. 09

    Containerised the stack with Docker Compose (front end, API, PostgreSQL) and delivered a weekly report to my supervisor.

Key challenges

Notifications without coupling

Absences, justifications and meetings all needed to notify users. I used Django post_save signals and a single Notification model with a generic foreign key, so a new trigger never touches existing code.

Data integrity

Recording the same student twice for the same session had to be impossible, so I enforced a unique constraint (session, student, date) in the database rather than only in the interface.

One platform, four audiences

Teachers, students, parents and school admins each see a different app. The JWT carries the role, the React routes are protected per role, and every endpoint checks permissions again on the server.

A complex form on a phone

Justifying an absence needs a choice, a text and a file. Splitting it into a step-by-step wizard, with 'Next' disabled until a step is complete, kept it usable on mobile.

Results

  • 7 screens delivered from mockup to code: teacher dashboard, attendance sheet, class report, student/parent mobile views, justification wizard and school-admin overview.
  • Back end of 13 Django apps, 16 models and 20+ documented REST endpoints, started in one command with Docker Compose.
  • Next steps I documented: real-time updates with WebSockets, server-side PDF generation and an automated test suite.

Tech stack

Django 4.2Django REST FrameworkSimpleJWTReact 18VitePostgreSQLDocker ComposeGitHub Spec KitFigmadraw.io

Skills demonstrated

Software architectureData modellingREST API designRole-based securityUI/UX in FigmaAutonomy

Want this kind of work on your team?

Available for a 6-month PFE internship from January 2027.

Get in touch