Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SdazaP/ruTournament/llms.txt

Use this file to discover all available pages before exploring further.

The Results View page (/dashboard/tournament/:id/view/results) is the public-facing display of all competition data. It is accessible from the tournament sidebar under Ver Resultados and is intentionally read-only — no edit controls, no authentication prompts. Competitors and spectators can open it on any device to follow results in real time as the organiser enters data on the same app instance.

​
WCA Results View

The WCA tab shows a ranked leaderboard for each category and round. Data is loaded directly from IndexedDB using the same calculateRulesStats and sortWCA functions used in the entry page, so the displayed ranking always matches what the organiser sees. Table columns (desktop):
ColumnDescription
#Rank badge — gold for 1st, silver for 2nd, bronze for 3rd
CompetitorFull name
T1 – T5 (or T1 – T3)Individual solve times with penalty display
BestFastest valid solve in blue
AvgCalculated average in green
Penalty display rules:
  • Clean solve — plain time string, e.g. 9.74.
  • +2 penalty — shown as 9.74 +2 = 11.74 on desktop; the penalised total only on mobile.
  • DNF — shown as (9.74) DNF on desktop (base time in parentheses); plain DNF in red on mobile.
  • Best single in a row is additionally bolded in green to distinguish it from the other solves.
Mobile view: On screens narrower than 768 px the table automatically switches to a card layout. Each card shows the competitor’s name, a Best badge (blue), an Avg badge (green), and a compact grid of individual times with coloured cells (green for the best single, red for DNF).

​
Red Bull Results View

The Red Bull tab displays the elimination bracket round by round. Each bracket round is rendered as a responsive grid of match cards. Match cards show:
  • Competitor 1 and Competitor 2 names with their individual solve times (T1, T2, T3).
  • Per-solve win highlighting — the winning time in each solve slot gets a green background.
  • Win count badges for each competitor (N victorias).
  • A green winner banner at the bottom of the card once a match is resolved.
  • Cards for completed matches have a green top border (border-t-4 border-green-500).
Clicking a match card opens a detail modal with the full time breakdown and a final result statement, for example: Alice gana el enfrentamiento. Seeding round: If the category includes a seeding round, it appears as the first entry in the round selector labelled “Clasificación”. The seeding view is a ranked table identical to the WCA leaderboard, with an additional green highlight for competitors who received a bye into the next bracket round. Both the WCA and Red Bull tabs provide Categoría and Ronda selectors at the top of their respective views. Use these to switch between events without leaving the page. The URL does not change when you switch categories or rounds — all navigation is in-memory. The Results View reads a ?tab=WCA / ?tab=RedBull query parameter on load to set the initial active tab, and an optional ?category=<id> parameter to pre-select a specific category in the WCA view. Pass these in the URL to deep-link to a particular event.

​
Sharing results

Because ruTournament stores all data in the browser’s local IndexedDB, results are only visible on the device and browser that was used to enter them. Sharing the URL with someone on a different device will show an empty tournament unless the app is hosted and the data has been exported/imported.
The Results View URL follows this pattern: 
<app-url>/dashboard/tournament/<tournament-id>/view/results
Share this URL with competitors and spectators. The page is fully responsive and works on mobile browsers. No login or account is required to view the page. For publicly hosted instances (e.g. on Vercel or Netlify): The Results View works for any visitor as long as the data was entered in the same browser on the same device as the host. If you are running the tournament on a laptop and the app is deployed to a public URL, open the app on your laptop to enter results — the data lives in your laptop’s IndexedDB and is not transmitted to any server. Visitors loading the same URL from their own devices will see an empty state. For fully local instances (running via vite dev or served locally): Only the organiser’s machine can access the results view.
Finalize the tournament after the competition ends by changing its status to Finalizado from the Dashboard panel. This locks all results, scrambles, and schedule data permanently and prevents accidental edits. The Results View continues to work normally after finalization.

​
Loading state

The Results View fetches tournament data asynchronously. While the IndexedDB query is in progress, a spinning loader is displayed. Once loaded, the page renders without a full reload — switching categories and rounds is instantaneous because all data is already in memory. If a round has no results entered yet, the table or match grid is shown empty rather than hidden, so spectators can still see the competitor list for upcoming rounds.

Build docs developers (and LLMs) love

Get started for freeTalk to us