The problem

HDTC needed a learning management system of its own rather than a rented seat on somebody else's platform: courses, and the accounts allowed to reach them, living in a database the organisation controls. The brief was explicitly about two things — scale, because the system had to keep working as content and users grew, and authentication, because access had to be genuinely enforced rather than a login form sitting in front of files anyone could guess the URL of.

My role

Freelance engagement, sole engineer. I built the platform end to end: the data model, the application layer, authentication and course management. Building an LMS alone forces a discipline that larger teams often skip — get the core right (courses, accounts, and who may reach what) and deliberately do not build the features nobody asked for, because every one of them is something you will maintain by yourself.

Architecture

• Laravel on the application side, which gives the project a conventional structure another engineer can pick up without a guided tour — migrations describing every schema change, an ORM over an explicit data model, and framework-level protection across the usual web attack surface.
• PostgreSQL as the datastore, for stricter typing and constraint handling. In a system whose entire job is deciding who may see which course, having the database enforce referential integrity is worth more than the convenience of a looser engine.
• Authentication designed as the access boundary rather than a formality: hashed credentials, server-side sessions, and authorisation checked on the course resources themselves instead of only on the pages that link to them.
• Course management modelled so that courses, their content, and the accounts entitled to them stay separate concerns — which is what lets the catalogue grow without reshaping the schema every time the organisation adds a programme.

Technologies

Laravel, PHP, PostgreSQL.

Outcome

HDTC has its own learning platform, with course management and secure authentication in place, on a stack it can hire for rather than a proprietary product it cannot leave. The scalability requirement was answered structurally instead of with hardware: a normalised PostgreSQL model and a conventional Laravel codebase mean growth is a question of adding content and indexes, not rewriting the system.