Label111
Fight Hub: a public register, the working area separate
How we built Fight Hub: a public register of fighters, gyms and galas, with the working area behind login.
Fight Hub is the public register of MoreFights: fighters, gyms, galas, rankings and a market of available fighters. Proposals and requests sit in the logged-in app.
Problem
Fans and gyms look up a record, a gym or a ranking. Promoters have to fill a card. Those two jobs do not belong on the same page. A public site that is only built in the browser gives search engines an empty page. A directory that invents slots is already stale the day after a card change.
Approach
Public pages for fighters, gyms, events, rankings and the market, rendered on the server from the data. The logged-in app for proposals and requests. Filament for federation admin and moderation. Taxonomy comes from the API, not from a list hardcoded in the front end.
What we built
What this proves for youA register has to be look-up-able. The workshop where gyms make matches belongs behind that, not on the homepage. What is not in the data does not appear on the page.TechnologyLaravel and Filament for taxonomy, records and moderation. React for the logged-in app. Public routes come from the same data, so a fighter or gym page is a real URL.
Technology: laravel, filament, react