Esport Club Management

Overview

I built this full-stack app for a school esports club (MRC) so membership, groups, events, and tournament grouping lived in a database instead of a noticeboard. Administrators add and update people, put them on teams, schedule what is next, and shape groups before a competition.

Source: MRC-EsportClub-DB. It is the earlier, school-shaped cousin of later event products (ELEGANZA ticketing, Profbot).

Problem

School clubs die in group chats. Lists go stale. Event dates live on a poster. Tournament groups are decided the morning of. A teacher or senior student needed a tool they could actually run without a SaaS bill.

What I built

Member CRUD — add, update, remove — with a single source of truth. Group management so practice and roles are not “whoever showed up.” Event scheduling with a path to notify members and think about attendance. Tournament grouping so teams and roles exist before match day.

The UI is server-rendered PHP with HTML/CSS/JS: forms, lists, and admin pages a club coordinator can learn quickly. MySQL holds members, groups, and events.

Impact

It modelled real school-club operations and left a public repo. Later esports and event-ops work in this portfolio starts from the same idea: members, events, competition structure. I do not invent membership totals.

Key features

• Member add / update / remove
• Member groups for teams and coordination
• Upcoming event scheduling
• Tournament grouping before match day
• Coordinator admin dashboard

Technologies

HTML, CSS, JavaScript, PHP, and MySQL — a server-rendered web app with a relational backend.

My role

Solo full-stack build for the school club: schema, admin UX, and the public repo.