Update Schedule page: Kings/Queens toggle + real game data #95
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#95
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 parent of a player, I want to see game schedules separated by Kings and Queens so I can plan around my child's season.
story:WS-S26
Context
Current
schedule.htmlhas all 5 Kings teams with TBD dates. Needs Kings/Queens toggle (same pattern as Tryouts and Teams pages) and real schedule data when available. Queens tournament info coming from Lucas soon.File Targets
Files to modify:
schedule.html— add Kings/Queens toggle. Kings side keeps current 5 teams. Queens side will have TBD placeholder until Lucas provides tournament info.Acceptance Criteria
Test Expectations
Constraints
shared/app.jsonce, reuse everywhereshared/style.cssChecklist
Related
westside-playground-overhaulScope Review: NEEDS_REFINEMENT
Review note:
review-410-2026-03-25Three fixable issues found before this ticket is agent-ready.
westside-appbut### Repofield sayswestside-playgroundand file targetschedule.htmlonly exists inwestside-playgroundtryouts.html(#92) norteams.html(#93) exist yet. #92 is the ticket that creates the toggle pattern — this ticket depends on it but doesn't document thatRefinements from review-410-2026-03-25:
Repo convention: Documented.
Depends on #92 (Tryouts). #92 creates the Kings/Queens toggle foundation. This ticket reuses the pattern — same
initKQToggle()JS, same.queens-activeCSS, same localStorage persistence. Addingdepends:ws-92.Untestable criteria resolved: "Same toggle pattern" and "Consistent toggle UX" are testable AFTER #92 lands. Agent should verify toggle HTML structure matches #92's implementation exactly.
No nav changes needed. Schedule already exists in the nav. This ticket only adds the toggle within the page.