LigaWerk: Digital League Management for Inline Hockey and Other Team Sports
What This Page Explains
LigaWerk brings the recurring work of league operations into one web application. Clubs, league management and administrators work with the same master data, registrations, schedules, game reports and reports.
This page explains which tasks LigaWerk covers and how the work areas fit together.
What LigaWerk Provides
| Area | Explained value |
|---|---|
| Master data | Association, clubs, teams, venues, people and functions are maintained once and reused across workflows. |
| Registrations | Teams, players, trainers, referees and officials are registered and reviewed for a season. |
| Competition operations | Season, league, schedule, dates, venues, results and standings stay connected. |
| Game report | Lineups, events, supplements, referee feedback and league decisions are handled traceably. |
| Communication | Game changes and briefings are addressed to the affected roles and documented with delivery status. |
| Demo access | Key roles can be tried through activatable demo access. The demo state is reset regularly to a defined starting point. |
| Data transfer and output | General import/export functions are not included as a finished standard scope because formats and target systems need to be clarified first. Initial data imports or concrete import/export paths can be implemented on request. |
| Public information | Schedules, standings, clubs, teams, glossary, handbook, legal pages and the source-bound Luminara chat are available as public pages. |
| Embedding | A finished embedding interface is not part of the standard scope. If an association or clubs want to reuse public master data or competition information on their own websites, the suitable output can be developed on request. |
Who Uses The Application
League Management and Association
League management prepares seasons, leagues, competition operations and review workflows. It sees registrations, open decisions, game reports, referee assignments and results waiting for approval in its workspace.
Clubs
Clubs maintain their master data, contacts, teams, player lists, trainers, referees and venues. They register data for the season and respond to follow-up questions or game changes.
Referees, Officials and Recorders
Referees and officials are managed with profile, role, availability and assignments. Game report recorders receive access to the games they need to prepare or edit.
Public Audience and Partners
Public pages show approved information: competition operations, clubs, teams, standings, statistics, glossary, handbook and legal details. Internal administration and review areas remain protected.
The Typical Flow
- Association, season and leagues are prepared.
- Clubs maintain master data, teams, people, trainers and venues.
- Teams, player lists and officials are registered for the season.
- League management reviews registrations and organizes schedule, dates and venues.
- Games are prepared, briefed, assigned and documented on game day.
- Game reports are reviewed; confirmed results feed standings and reports.
- Public pages show the approved state.
Core Work Areas
Master Data and Roles
Master data is the foundation for all later steps. Clubs, teams, people, functions, memberships, trainer profiles, referee profiles and venues are maintained so they can be reused in registrations, assignments and public pages.
Season, League and Registrations
Seasons, leagues and team registrations structure competition operations. The application separates preparation, review and confirmed participation, so it remains clear which state is only submitted and which state is approved.
Schedule, Game Report and Result
Game dates, venues, lineups, periods, events, supplements and review decisions stay connected. Only confirmed results affect standings and reports.
Licenses and Review Office
Pass and license data, applications, documents, follow-up questions, access records and decisions are kept in a traceable review context. Clubs see where feedback is required; the review office sees what must be decided.
Communication and Audit Log
Game changes, briefings and follow-up questions are addressed to the affected roles. Saved changes by signed-in users are recorded in the audit log, so decisions and data states remain traceable.
Traceability
LigaWerk separates domain roles and workspaces. This matters because league operations are not only data maintenance; they also make decisions, approvals and responsibilities visible.
The audit log records who triggered a saved change, which record was affected and in which work context the change happened.
Public Information
Public pages explain league operations and show approved data. They include master data, competition operations, standings, statistics, glossary, handbook and legal information.
The current public page set is consolidated: home page, feature overview, demo access, glossary, legal pages, competition operations, leagues, master data and handbook follow the same calm UI foundation and focus on usable navigation, clear typography and traceable detail pages.
As of 2026-07-08, the public area also supports theming: Light and Dark can be selected through a compact header control, language selection remains visible on detail pages such as master-data club and league pages, and the preference is carried over when switching into the admin area.
Internal administration, review and support functions remain limited to signed-in roles.
Demo And Interface
The current public state includes activatable demo access for central work roles: system administration, league management, club management, trainer/team management, referees/officials and game report recording. Each access starts through a one-time login link.
The demo state is intentionally resettable. Changes made in demo access are only meant for trying the system and are replaced by the initial ZauberForest demo state during the next demo reset.
In parallel, a shared UI foundation is taking shape. The public area now uses global tokens for typography, spacing, radii, surfaces, lines, status colors and dark mode. The admin area follows the same CI direction through EasyAdmin Light/Dark tokens, keeping status surfaces, table rows, cards and workspace context adjustable as one system.
As of 2026-07-11, additional admin workflow surfaces have been aligned in dark mode and the game-report correction flow has been clarified: license filters and withdrawal dialog, referee and availability views, license review contexts, team image management, My assignments, license application lists, roster/team-player routes, the add-member form and empty EasyAdmin detail values follow the shared admin tokens and EasyAdmin patterns; recorders see correction tasks, can add a comment when resubmitting and then see the saved comment in the cockpit. Planned seasons are now reachable in the admin area as preparation state without becoming publicly active; the demo seed includes a half-prepared WaldLiga 2027 with planned leagues, mixed team and player registrations, referee registrations and four planned games.
In parallel, the AI assistant has started as its own preparation stream. As of 2026-07-13, the internal admin preview has become a real chat pilot: chat history is kept per session as Markdown, answers use the configured answer LLM when available, and a server-side harness limits sources, small talk, out-of-scope replies and mutation refusals. Safe Markdown answers may include controlled internal navigation links; source details now show only real page links such as glossary or handbook pages, not technical content files.
As of 2026-07-15, Luminara is live as a public chat on approved content pages. The chat opens as an inline area below the header, pushes page content down, uses the Ask Luminara pull tab and keeps the logo as the normal home link. Answers use the source-bound public assistant endpoints with streaming, CSRF protection, limited history and public source links. The visible conversation is kept across public page changes for the current browser session and is cleared only by Restart chat or the end of the session. On mobile, the Luminara image and persona details sit compactly next to each other, while the chat uses the full width below.
As of 2026-07-18, Luminara is also available in the admin area as a read-only help drawer for operational roles and has been tightened through live testing. It uses workspace, role, current route, current path and approved view metadata to explain the current page first and then point to suitable next steps or neighboring areas. The admin guide is covered especially for game reports, registrations, tables, license register, season/league and association data; new admin routes receive an automatic baseline description. Suggested questions are shown only when they clearly match the current view.
Data Exchange And Embedding
Imports and exports are currently not implemented as a generic standard module. This is intentional: for master data, schedules, game reports, standings or further data, the right format depends on who needs the data, which source system is involved and how the data will be used afterwards.
When a concrete need appears, initial data imports can be handled or suitable import/export paths can be developed. This keeps LigaWerk open for CSV, Excel, technical interfaces or project-specific formats without promising unnecessary variants in advance.
The same applies to integrating public information into existing websites. A finished general embedding interface is not included up front. On request, a suitable output can be developed so associations or participating clubs can show approved master-data and competition information on their own sites.