01 — brief
Why they reached out
An established league running on spreadsheets reached out to me after my work on Royalty Series. Everything is manual, their history is spread across different files, and it makes it difficult to scale in future seasons. They need a real platform.
02 — architecture
How the system is set up
platform architecture
Select a part to see what it does and how it connects.
API and web app in TypeScript · Railway
03 — scope
What it needs to do
01
League and season structure
02
Team and roster management
03
Scheduling and match reporting
04
Standings and statistics
05
Roles and permissions
06
Deployment and release process
04 — status
In alpha with league stakeholders, with regular progress updates.
I’m the only developer, so I make the architecture decisions and I’m accountable for them. The full case study will be posted once the league has run a season on it.