S.L.S STEM & Robotics Learning Platform
A custom academy platform connecting public program discovery with registration, teaching, parent/student portals and day-to-day STEM operations.
العربيةSeparate applications for different operational needs. Explore the other S.L.S project
Running practical STEM programs involves more than publishing course pages. Families need clear pathways and registration, instructors need schedules and learning tools, and the academy needs a consistent view of enrollments, attendance and course finances.
The platform brings these journeys together while keeping STEM operations separate from the school's Student Affairs and administrative systems. The public experience introduces Scratch, MATE ROV and RoboCupJunior pathways; role-based workspaces support the academy's learning and operational tasks.
React and TypeScript power the frontend, with Node.js/Express APIs and MongoDB persistence. Role-specific routes separate administration, accounting, academy management, instruction, students and parents. The case study uses the project's own stack, not the Next.js/PostgreSQL stack of this portfolio website.
- Arabic/English program discovery, grade-based pathways and seasonal registration
- Course, section, timetable and enrollment management
- Instructor, student and parent workspaces
- Attendance, assignments, learning resources and progress views
- Certificate generation and verification routes, with XP and achievement modules
- Course payment records, expenses, financial reports and distribution workflows
Representative journey: discover a program → review the eligible pathway and available sections → register → manage enrollment → support learning and attendance → review progress and certificates. This is a workflow explanation, not evidence that every private role was retested during this portfolio review.
The current repository defines six STEM roles: admin, accountant, academy manager, instructor, student and parent. Historical descriptions of school HR, Student Affairs and Control are not part of the current STEM case study.
The school website and its parent/Student Affairs services are presented as a separate project. Public interface captures demonstrate program discovery; diagrams explain source-documented workflows and are not fabricated dashboard screenshots.
Want a system like this for your business?
Tell us what you are trying to achieve. We will help you clarify the next practical step.