Qyzen Learning Platform
A learning website for schools where admins, teachers, and students share one place for classes, tests, and grades.
- Role
- Product design + full-stack development
- Outcome
- Each person sees only their own school work, all kept in one shared place.
- Stack
- LaravelPHPMySQL
What it is
Qyzen Learning Platform is a learning website for schools. Admins, teachers, and students all work in one shared place for school records.
Admins set up the school structure and user accounts. Teachers organize classes, tests, grades, learning materials, and announcements. Students study, take tests that are graded automatically on the server, and check their records. Each role gets its own home page and menu for its daily work, but everyone works from the same school years, terms, sections, subjects, enrollments, tests, and grades.
Shared calendars, notifications, profiles, and private messages keep planning and communication together, instead of spread across separate tools.
The problem and the fix
The problem
Work spread across many tools
Admin screens, class lists, test tools, spreadsheets, and file storage were not connected
Privacy and fairness risks
The wrong people could see data, and grading could be tampered with on a student's device
Records could get lost
Imports, exports, archives, and backups had no single reliable home
The fix
Built around the school year
School years and terms hold sections, subjects, and enrollment before tests and grades
A space for each role
Admins, teachers, and students share one system but each has their own home
The server checks everything
Access rules, grading on the server, and private files
School records kept safe
Checked templates, exports, archives that can be restored, and reliable storage
What I did
- Planning a separate path for admins, teachers, and students, from first sign-in to daily school work.
- Connecting every button and form to the server for accounts, classes, tests, grades, materials, notifications, and messages.
- Protecting each role so people only reach their own pages and data, and students only see classes they are enrolled in.
- Keeping records safe with spreadsheet import and export, archives that can be restored, reliable file storage, and backup tools.
- Checking the work with 374 PHPUnit tests covering 1801 checks, plus a successful Vite production build.
The work covered planning the product, building it with Laravel, keeping the screens consistent with Tailwind and Metronic KTUI, and making sure every page shows only what the viewer is allowed to see, for their classes and at the right time.
How I designed it
- 01School year
Start with the school year
School years and terms hold sections and subjects, then enrollment, question banks, and tests follow
- 02Consistency
Reuse the same screen patterns
Tables, pop-ups, alerts, date pickers, calendars, and editors work the same for every role
- 03Speed
Send only what the page needs
The server sends a full page or just the part that changed, with no public API
- 04Security
Protect each role on the server
The server controls who sees what, grades every test, and keeps files private
- 05Records
Make records safe and restorable
Checked imports, exports, archives, and restores keep school records safe
Main features
Setup and new accounts
Admins add and manage users and roles, set up school years, terms, permissions, and settings, and add many accounts at once from spreadsheet templates. If a row has a mistake, the import points it out.
Teacher workspace
Teachers create sections and subjects, manage enrollment, build question banks, put together tests, assign work to classes, grade submissions, and share grades and feedback with their enrolled students.
Taking tests as a student
Students see only the classes they are enrolled in and the work assigned to them. They take tests while signed in, submit once for grading on the server, and then check their grades, records, and related messages.
School records
Grades, enrollment history, and test results stay linked to school years, terms, sections, and subjects. Records can be exported to Excel, and archives can be restored when a new term starts.
Materials and announcements
Learning materials and announcements belong to specific sections and subjects, are stored privately behind sign-in, and show up the same way for every role.
Shared planning and messages
Calendars, notifications, and private messages are available to every role, and each person only sees what their role allows. This keeps planning and messages linked to school records instead of scattered across other tools.
Tech Stack
PHP 8.3 & Laravel 13
the backend: pages, access rules, and the logic for each role.
Blade, HTML, CSS & JavaScript
pages built on the server, with extra features added in the browser and shared screen patterns.
Tailwind CSS 4 & Metronic KTUI
styling and ready-made building blocks for tables, pop-ups, and calendars.
Vite
the development server and building the final frontend files.
SQLite & MySQL
the databases, with migrations, factories, and seeders for each setup.
Laravel Fortify & Socialite with Google OAuth
email and password sign-in, plus Sign in with Google.
Laravel Mail with Gmail SMTP, Maatwebsite Excel, PhpSpreadsheet, Quill, Flatpickr & FullCalendar
emails, spreadsheet import and export, rich text editing, date picking, and calendars.
PHPUnit & Echo with Pusher and Reverb
374 tests with 1801 checks, plus optional live updates that fall back to regular checking.
There is no public API. The server sends pages, plus small internal JSON and HTML updates for the website. Google sign-in, email, and live updates only work when they are set up.
Hard parts and how I solved them
- Keeping each role's data separate
- Access rules, ownership checks, and enrollment checks on the server stop one role from seeing another's data. Separate home pages and menus also make it harder to open the wrong thing by accident.
- Keeping tests fair
- Grading happens only on the server. Submissions are checked against enrollment and deadlines, and questions and answers are only shown when allowed, so nobody can change their results from their own device.
- Supporting real school work
- Spreadsheet templates that are checked on import, clear import error messages, Excel exports for tests and grades, reliable storage for materials, and archives with restore and backup tools all match how schools really add and keep their data.
- Working on different hosting setups
- Files are kept private instead of on a public folder. Live updates through Echo with Pusher or Reverb quietly switch to checking for updates every so often when the host does not support them.
How it works
- 1
Every role opens its own home page and menu for its daily work.
Admins start with users, roles, and terms, teachers with sections and tests, and students with their classes and pending work, all inside one shared record system.
- 2
Learning follows the school year from start to finish.
School years and terms hold sections and subjects, enrollment places students in classes, question banks feed tests, submissions are graded on the server, and grades stay visible to enrolled students.
- 3
The server makes sure each person only sees their own space.
Access rules limit the data, grading on the server stops cheating from a student's device, and private files are only shared after sign-in and permission checks.
- 4
School records stay safe through imports, exports, archives, and backups.
Checked spreadsheet templates allow adding many accounts at once, Excel exports include tests and grades, archives can be restored, and reliable storage with backup tools protects uploaded files and materials.
- 5
It is a website powered by Laravel and a database.
There is no public API; the server sends full pages or small internal JSON and HTML updates, and Google OAuth, email, and live updates through Echo with Pusher or Reverb only work when they are set up.
Results
- Admin, teacher, and student tasks work from start to finish inside one shared record system.
- 374 PHPUnit tests with 1801 checks passed, covering permissions, who can see which classes, grading, and learning materials.
- The Vite production build finished successfully.
- No numbers on users, ease of use, or business results are claimed, because none were measured.
- Browser support, going live on a host, and the Google, email, and live-update features depend on setup and were only checked by automated tests.
What I learned
What worked
- Treating permissions, ownership, deadlines, and record keeping as part of the design keeps each role's view honest and predictable.
- Planning around school years, terms, sections, subjects, enrollment, and tests before polishing screens kept everything connected.
- Reusing the same tables, pop-ups, alerts, date pickers, calendars, and editors for every role kept the look and feel consistent.
- Checked imports and exports, reliable storage, archives, and backups matched what schools really need.
What could improve
- Show clearer messages when an import, a file save, or an archive fails, so problems are never silent.
- Explain more clearly how to set up Google OAuth, email, and live updates for whoever hosts the site.
- Test the calendar, editor, and announcements more with screen readers and on phones.
- Try the full path from enrollment to grading to records on a real host to confirm private files and update checks work.
Future ideas
- Clearly mark which features depend on setup and which always work.
- Give better guidance on storage limits, how long to keep files, and how to recover exports and archives.
- Keep improving live updates so they switch off smoothly when the host does not support them.
- Keep planning around the school year when adding new kinds of school structures.


