Skip to content

Ringside

A wrestling promotion management platform for booking events, managing rosters, tracking championships, and organizing storylines.

Visit the project (opens in a new tab)
Ringside The Laravel Architect
Ringside project preview

Project overview

Built with

  • Laravel
  • Livewire
  • PHP
  • Pest
  • Larastan
  • Tailwind CSS
  • MySQL

Areas of focus

  • PHP
  • Laravel
  • Architecture

Project story

The problem

Independent wrestling promotions often rely on spreadsheets and disconnected tools to manage rosters, contracts, events, matches, titles, and storylines. That makes complex business rules difficult to model and easy to lose.

The solution

Ringside is a full-featured management platform built around the way wrestling promotions actually operate. It brings roster management, contract tracking, event booking, championship lineage, match results, and storyline planning into one focused workspace.

Highlights

  • Reactive roster, event, and match workflows built with Laravel and Livewire
  • Action-based architecture for business operations
  • Eloquent relationships for championship histories, faction memberships, contracts, and event cards
  • Computed wrestler status based on real employment and career data
  • Pest browser coverage, Larastan static analysis, and Rector automation

The result

Ringside turns a promotion's operational data into a connected system instead of a collection of spreadsheets. It is also the project where I have sharpened my skills with action classes, complex domain relationships, and domain-driven design patterns.

Read and listen to more work connected to this project.

Laravel · · 7 min read

How I Decide What to Test in Laravel

I start with what a test should prove, then choose the boundary that can prove it. This is how I separate Unit, Integration, Feature and browser tests without making every test do the same job.

Laravel · · 7 min read

How I Handle Authorization in Laravel

I separate who a user is from what they're allowed to do. Gates and policies organize the permission rules, but the server still has to enforce them before the operation runs.

Laravel · · 8 min read

How I Use Laravel Queues

I use queues to move work out of the request, but dispatching a job is only the handoff. I still need a worker, a safe retry, and a way to know whether the work finished.

Have a similar challenge?

Tell me what you’re building, what needs to change, or where you’re stuck.

Discuss a similar project