One Rating That Follows a Player From Friday Nights to Canton
Hall Of Football runs a rating system spanning high school, college, the professional game, and the Hall of Fame, with editorial coverage published alongside it. A name can be tracked across all four stages on one site instead of across four unconnected outlets.
Project: Hall Of Football · Sports media & ratings
Project Overview
Sector: Sports media
Industry context: American football coverage from high school through to the Pro Football Hall of Fame
Product: Hall Of Football, a web platform combining player ratings with editorial publishing
Positioning carried on the site: the best of the best, from small towns to Canton
Build focus: A rating system across four levels, editorial publishing, member accounts, site-wide search
American football is covered exhaustively and in fragments. Recruiting sites own high school. College outlets own the college game. Draft coverage owns the transition. Professional media owns the rest. Hall Of Football was built on the premise that the interesting story is the line running through all four, and that no existing outlet is positioned to tell it.
Key Features
A Rating That Spans the Whole Sport
Prep, college, professional, and Hall of Fame assessments held in one framework rather than four incompatible ones. The gain is continuity, making a player’s development readable as a single line and early evaluations checkable against later outcomes.
Numbers Next to the Reporting
Latest ratings, a lead feature, and current news presented together rather than in separate sections. The gain is context, since a reader sees what moved a rating at the moment they see the rating move.
Built for Returning Readers
Member accounts store reader interests, while search provides direct access to any player or story—creating a more personalized experience and stronger retention across seasons.
Inside the Product
Measure the Whole Career
Building one measurement framework across four levels of a sport is a data modelling problem before it is a publishing one, and worth resolving in that order.
Scoping happens in days. Working software follows in months. A senior engineer owns the architecture from the first conversation through to release.