New page: Teams — public rosters with Kings/Queens toggle + profile gate #93
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/westside-landing#93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Part of public site evolution. Parent note:
westside-playground-overhaulRepo
forgejo_admin/westside-playgroundUser Story
As a prospective parent, I want to see team rosters so I understand the program's depth and structure.
story:WS-S26
Context
Public-facing team roster page. Kings/Queens toggle at top. Shows each team's roster with player photos and names — BUT only for players with complete profiles. Players with incomplete profiles are not featured publicly (in production, they get emailed to complete their profile).
In the playground mock, show some players as visible and others as a "profile pending" placeholder to represent the gate concept.
File Targets
Files to create:
teams.html— Kings/Queens toggle. Per-team sections showing: team name, division, coach, and player cards (photo + name + number). Mock data — use realistic team names from schedule (16U Elite, 17U Elite, 17U Select, 16U Local, 17U Local for Kings; Queens teams TBD).Acceptance Criteria
teams.htmlexists with Kings/Queens toggleTest Expectations
Constraints
shared/style.cssandshared/app.jsChecklist
Related
westside-playground-overhaulScope Review: NEEDS_REFINEMENT
Review note:
review-408-2026-03-25Three fixable issues found before this ticket is agent-ready.
forgejo_admin/westside-playgroundbut is filed onforgejo_admin/westside-app. Agent will see conflicting repo signals./tryoutshas no Kings/Queens toggle. Board item #407 (Tryouts with toggle) is also intodoand hasn't landed. The pattern doesn't exist yet.teams.html. The 6 public-nav pages (index.html,staff.html,sponsors.html,schedule.html,register.html,success.html) should be enumerated.Refinements from review-408-2026-03-25:
Repo convention: Documented.
Depends on #92 (Tryouts). #92 creates the Kings/Queens toggle foundation (JS, CSS, localStorage). This ticket REUSES that pattern. Adding
depends:ws-92.Nav file targets (explicit): Add "Teams" to nav on:
index.html,about.html,staff.html,tryouts.html,sponsors.html,schedule.html,register.html,success.html— plus any new pages that exist at merge time.teams.html vs team.html:
team.html(singular) is the authenticated single-team detail page.teams.html(plural) is the new public roster listing. No conflict.Queens pink color: Automatically handled by the
.queens-activeCSS from #92. No extra work needed in this ticket beyond using the same toggle HTML pattern.