Menu Item Reference

Create public pages under Menus → [your menu] → New → JoomLeague. Select and save required project-dependent fields before expecting dependent entry selectors to populate. Publish the menu item only after its source records are published.

Overview and directory items

About: no selection; component/release information.
Projects: no selection; all accessible published projects.
Project: requires project_id; one project overview.
Clubs: no selection; searchable/filterable club directory.
Club: requires club_id; one club and its teams.
Teams: represented through club/project directories; use Team for a direct detail item.
Team: requires team_id; one reusable team record.
Person: requires person_id; one person and current memberships.
Venues: no selection; searchable/filterable venue directory.
Venue: requires venue_id; one venue detail.
Personnel: requires project_id; project staff and officials.

Participant items

Participants: requires project_id; all published entries, including teams, individual people and groups.
Participant: requires project_id and entry_id; one entry and current roster/memberships.
Participant Statistics: requires project_id and entry_id; statistics associated with one entry.

The entry selector depends on project context. Save/select the project first when Joomla cannot populate both fields during the initial unsaved menu form.

Programme items

Results: requires project_id, optional stage_id; programme/results overview grouped by round. show_venue controls location detail.
Programme Item: requires match_id; direct detail for one programme record. Existing installations may retain this route, while normal overview links use Event Report.
Event Report: requires event_id; complete operational report.
Next Event: requires project_id; nearest upcoming event.
Team Plan: requires project and entry; configurable all/upcoming/played scope, ordering, limit, next highlight, round, venue and calendar.
Club Plan: requires project and club; the same controls across all of a club's participating teams.

Standings and analysis items

Standings: requires project, optional stage. Configure scope, metrics, highlighted entry/style, row limit, combined score columns, short labels, responsive behavior, top/bottom zones and recent form.
Standing Progression: requires project, optional stage; rank development over completed programme items.
Result Matrix: requires project, optional stage; participant-by- participant result matrix for compatible head-to-head contests.
Comparison: requires project; comparison of selected entries.
Bracket: requires project and stage; multi-round knockout progression.

Ranking items

Event Ranking: requires project; occurrence ranking from recorded event types.
Statistic Ranking: requires project; ranking by a selected/available numeric statistic.
Statistics Overview: requires project; catalog and leaders across the project's recorded statistics.

Choosing compatible views

JoomLeague exposes a universal menu catalog, but not every view is meaningful for every sport. Use profile capabilities and project data:

a race can use programme, participants, results, statistics and race-result standings without a home/away result matrix;
a knockout cup can use a bracket only after rounds and final progression results exist;
an individual tournament uses person entries rather than forcing teams;
an event report can represent more than two participants and must retain sport-neutral programme terminology.

Create the project's primary overview and the detail menu items required for stable SEF routing. Publish JoomLeague Project Navigation alongside them; it exposes only sections available for the selected project/profile. This is more maintainable than duplicating a hard-coded submenu in every template.

After creation, test links with SEF enabled and disabled, then as an anonymous visitor. A working non-SEF component URL does not guarantee that an unpublished parent menu item has a valid public route.

See Results and Event Report for the administration workflow that supplies every section of this public detail.

Menu parameters form the final presentation layer. Template Settings and Inheritance explains when a setting belongs to the profile, project, menu item or module.