Tournament for TYPO3

Sports clubs run their tournaments in Excel, even though their website is the natural home for results and standings

Every weekend, thousands of club tournaments take place across Europe. Results are typed into Excel sheets, uploaded to the website as PDFs or, at best, entered by hand into an HTML table. Visitors to the club website see outdated data because nobody updates the page. The TYPO3 Tournament extension replaces this workflow: groups, fixtures, results and standings are managed directly in the CMS. Enter a result, and the standings update automatically. For sports clubs, esports organizations and companies that run internal competitions, this delivers a professional presentation without any programming effort.

The typical formats are football tournaments, esports leagues and company competitions

The most common scenario is a sports club’s football (soccer) tournament. Sixteen teams compete in four groups. Each group plays a round robin, and the top two teams advance to the knockout stage. The extension covers this format completely: a group stage with points, goal difference and head-to-head record, followed by a knockout stage with quarterfinals, semifinals and a final. Results are entered in the backend, and the standings and the tournament bracket update automatically in the frontend.

A second scenario is esports leagues. A gaming club organizes a Counter-Strike league with 12 teams and a season of 20 match days. The extension manages the league table, the schedule and the results history. Every team gets a profile page with roster, statistics and past results. The presentation follows the club’s own branding, not the layout of a third-party platform.

Third scenario: internal company competitions. A company with five locations holds an annual chess tournament. Employees sign up through the TYPO3 intranet, the extension draws the pairings and shows the progress of the tournament live. It is a niche application, but a real use case for companies that want to encourage engagement and exchange across their locations.

Tournaments are modeled as a nested record structure

The extension defines several Extbase models: Tournament, Team, Group, Match and Result. A tournament contains groups, and each group contains teams. Matches are either generated automatically (round robin) or defined manually (knockout stage). Results are stored as Result records linked to their match.

Standings are calculated on the server: points (3-1-0 or configurable), goal difference, goals scored, head-to-head record. The sorting logic is configurable via TypoScript, because different sports prioritize different criteria (football: goal difference before goals scored; handball: goal difference or head-to-head results first, depending on the competition).

The frontend renders two main views: the group stage as a table (teams, points, wins, losses, goal difference) and the knockout stage as a nested bracket. The bracket is built with CSS as a tree structure that runs horizontally on desktop and vertically on mobile devices.

For larger tournaments with livestream integration, the extension can be extended with AJAX: results are entered in the backend, and the frontend updates the score by polling every 30 seconds, without reloading the page.

Common problems involve tournament format logic and bracket display

The biggest problem is the sheer variety of tournament formats. A simple knockout tournament with 8 teams is trivial. But a Swiss-system tournament with 40 teams, a double-elimination format or a league with promotion and relegation rounds requires complex logic that not every extension supports. The tournament format has to be clearly defined before you choose an extension. If the extension does not support the required format, a custom extension of its functionality is needed.

Second problem: displaying the bracket on mobile devices. A knockout bracket with 16 teams has four rounds (round of 16 through to the final). This tree structure does not fit on a screen 375 pixels wide. Horizontal scrolling or a simplified list view are the pragmatic solutions.

Third issue: team photos and crests. Clubs want logos next to the team names in the standings. The extension has to offer FAL integration for team images; otherwise editors have to type image paths by hand.

Tournament extensions are niche products with a limited community

Tournament extensions for TYPO3 are niche solutions with a small community. Current versions run stably under TYPO3 v12. Further development for v13 is not guaranteed, because the maintenance effort is hard to justify economically for the maintainer of a niche extension. Clubs planning for the long term should assess whether a specialized tournament platform (Challengermode, Toornament) connected to the TYPO3 website via API would be more sustainable than a monolithic extension. Gosign advises clubs and organizations on the choice between a community extension, custom development and SaaS integration.