project 14
Anadolu Diabetes School
A multi-module education platform for people with diabetes and their families. It brings together public pages, a lesson and student panel, course sales through a cart and order flow, an admin panel, and a separately authenticated Chronic Guide module.
- Category
- Web
- Role
- End-to-end development and deployment
technologies used
- Laravel
- PHP
- MySQL
- Blade
- Bunny Stream
- cPanel
problem
Problem
The organisation's existing site was a plain brochure page, with no infrastructure to publish educational content, track student progress or sell courses. There was also a hard technical constraint: the organisation's shared hosting package did not allow video hosting, yet lesson videos were the very core of the platform.
solution
Solution
I rebuilt the site from the ground up as a multi-module platform: public pages, a student panel serving the free lessons, a sales layer with cart and order flow, an admin panel for content management, and a separately authenticated Chronic Guide module. I solved the video constraint by hosting files on Bunny Stream — when an admin uploads, the file travels directly from the browser to Bunny and never passes through the hosting server. Finally I migrated the platform to cPanel, switched the DNS and took it live with SSL.
outcome
Outcome
The platform is live at anadoludiyabetokulu.com with a valid SSL certificate. The organisation updates lesson content, page copy and course structure itself through the admin panel, and the video infrastructure runs entirely independently of the hosting constraint.
key features
- 01Multi-module platform architecture running the student panel, lesson tracking and content management together.
- 02Lesson videos hosted on Bunny Stream — the file goes straight from the user's browser to the service, never touching the server.
- 03Course sales infrastructure built around a cart and order flow.
- 04An independent Chronic Guide module with its own login and permissions.
- 05Migration to cPanel and deployment to production with an SSL certificate.
why these choices
Why Bunny Stream?
Shared hosting packages don't allow video hosting, and even if they did, the bandwidth would run out after the first hundred viewers. With Bunny Stream the file uploads straight from the user's browser to the service, so the server carries neither the storage nor the bandwidth load.
Why the move to MySQL?
Development started on PostgreSQL, but the organisation's cPanel hosting offered MySQL. Matching the development database to production removed any surprises during migration.
Why is Chronic Guide a separate module?
It served a different audience with a different access model. Building it with its own login and permissions, rather than embedding it in the main platform, let both sides evolve without affecting each other.
Why Laravel?
Student accounts, authorisation, the order flow and the admin panel were all built on structures the framework already provides. It also runs at no extra cost on the organisation's existing cPanel hosting.