Fast Or Nothing (FON) is a racing organization in Puerto Rico. They run drag races, roll races, time attacks, and drift events across multiple tracks. Their admin platform manages the operational side: events, driver registrations, users, race specs, categories, and tournament configuration.
Why a rebuild
The previous platform was not just outdated -- it was structurally degraded. The codebase was difficult to navigate, the UI lacked hierarchy, and basic operational tasks took too many steps. Navigation was unclear, data-dense screens were flat, and the overall experience worked against the people who used it daily.
Patching was not viable. The old codebase had reached a point where maintaining it cost more than replacing it. The decision was a full rebuild.
Architecture decisions
- Angular for the frontend -- its opinionated module structure enforces consistency, which matters when multiple people maintain an admin platform
- Multi-tenant -- FON operates across multiple tracks, each with isolated data and configurable permissions
- End-to-end authorization -- tenant-aware module access with dynamic permissions across backend and frontend
What changed
The rebuild touched every screen -- events, users, specs, categories, tournaments, registrations. Every module was redesigned with consistent layout patterns, proper data tables, inline actions, and clear navigation hierarchy. Here are two examples from the events module:
Events list
The old version showed a flat screen with cards, thumbnails, and a search bar -- no way to filter by status. The new version has tabbed navigation (Current, Upcoming, Past Events), a proper data table with race styles, dates, runner counts, and inline actions.
Event details
The old detail page scattered metadata across cards with inconsistent layouts. The new one organizes event identity, dates, track, race styles, capacity, pricing per day, discount codes, registration status, and tournament details into structured blocks.
Full scope
The same pattern was applied across the entire platform:
FON Admin
├── Events ────── list, detail, creation, editing
├── Users ─────── roles, permissions, multi-tenant access
├── Specs ─────── vehicle specs linked to race categories
├── Categories ── race style definitions and rules
├── Tournaments ─ bracket config, scoring, standings
└── Registrations ─ driver sign-up, capacity, payment status
- Multi-day events with per-day pricing and discount codes with usage tracking
- Race styles: Drag, Roll Race, 1/4 Mile, Time Attack, Drift
- Driver registration with capacity enforcement
- Tournament bracket and scoring configuration
Fast Or Nothing (FON) es una organizacion de carreras en Puerto Rico. Organizan drag races, roll races, time attacks y drift en multiples pistas. Su plataforma admin gestiona el lado operativo: eventos, registros de pilotos, usuarios, specs de vehiculos, categorias y configuracion de torneos.
Por que reconstruir
La plataforma anterior no solo estaba desactualizada -- estaba estructuralmente degradada. El codebase era dificil de navegar, la UI carecia de jerarquia, y las tareas operativas basicas tomaban demasiados pasos. La navegacion era confusa, las pantallas con datos densos eran planas, y la experiencia general trabajaba en contra de quienes la usaban a diario.
Parchear no era viable. El viejo codebase habia llegado a un punto donde mantenerlo costaba mas que reemplazarlo. La decision fue una reconstruccion completa.
Decisiones de arquitectura
- Angular para el frontend -- su estructura opinionada de modulos impone consistencia, algo importante cuando multiples personas mantienen una plataforma admin
- Multi-tenant -- FON opera en multiples pistas, cada una con datos aislados y permisos configurables
- Autorizacion end-to-end -- acceso a modulos con awareness de tenant y permisos dinamicos entre backend y frontend
Que cambio
La reconstruccion toco cada pantalla -- eventos, usuarios, specs, categorias, torneos, registros. Cada modulo fue rediseñado con patrones de layout consistentes, tablas de datos apropiadas, acciones inline y jerarquia de navegacion clara. Aqui hay dos ejemplos del modulo de eventos:
Lista de eventos
La version anterior mostraba una pantalla plana con cards, miniaturas y una barra de busqueda -- sin forma de filtrar por estado. La nueva version tiene navegacion por tabs (Eventos Actuales, Proximos, Pasados), una tabla de datos con estilos de carrera, fechas, conteo de pilotos y acciones inline.
Detalle de evento
La vieja pagina de detalle dispersaba los metadatos en cards con layouts inconsistentes. La nueva organiza identidad del evento, fechas, pista, estilos de carrera, capacidad, precios por dia, codigos de descuento, estado de registros y detalles de torneos en bloques estructurados.
Alcance completo
El mismo patron se aplico en toda la plataforma:
FON Admin
├── Eventos ────── lista, detalle, creacion, edicion
├── Usuarios ───── roles, permisos, acceso multi-tenant
├── Specs ─────── especificaciones de vehiculos ligadas a categorias
├── Categorias ── definiciones y reglas de estilos de carrera
├── Torneos ───── configuracion de brackets, puntuacion, standings
└── Registros ─── inscripcion de pilotos, capacidad, estado de pago
- Eventos multi-dia con precios por dia y codigos de descuento con tracking de uso
- Estilos de carrera: Drag, Roll Race, 1/4 Milla, Time Attack, Drift
- Registro de pilotos con control de capacidad
- Configuracion de brackets y puntuacion de torneos