Public pages
The SEO and marketing routes — indexable, outside the dashboard shell, and on their own layouts.
Two route groups outside (dashboard), each with its own layout, because
neither wants the app shell's nav rail and filter bar.
(seo)
| Route | What it is |
|---|---|
/odds-converter | Fractional, decimal and American. A real tool |
/player-stats | A landing page — marketing copy and a localised FAQ |
/team-stats | The team-shaped twin |
The converter does work; the other two fetch nothing and show no leaderboard. They exist to rank, and saying so here saves the next person the ten minutes of looking for the data layer that is not there.
(marketing)
| Route | What it is |
|---|---|
/lineup-bot | The Telegram lineup bot, sold separately |
/odds-api | API access, sold separately |
They are still translated
Being outside the dashboard does not exempt them from
statshub-i18n — the FAQ on /player-stats is
localised, which is most of the point of it existing.
Entity pages
A fixture, team, player or referee — the detail pages, the lookup lists in front of them, and why only the trailing id resolves.
Architecture
How a page in the product site is put together — the route groups, the shell it mounts into, the portal targets a board fills, and the hand-over from legacy.