Update Schedule page: Kings/Queens toggle + real game data #95

Closed
opened 2026-03-26 23:50:10 +00:00 by forgejo_admin · 2 comments

Type

Feature

Lineage

Part of public site evolution. Parent note: westside-playground-overhaul

Repo

forgejo_admin/westside-playground

User 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.html has 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

  • Kings/Queens toggle at top of page
  • Kings shows current 5 teams with schedules
  • Queens shows placeholder (TBD — data coming)
  • Same toggle pattern as Tryouts and Teams pages
  • Consistent toggle UX across all 3 toggled pages

Test Expectations

  • Toggle switches content
  • All links resolve
  • Visual on 390px

Constraints

  • Same toggle JS pattern — add to shared/app.js once, reuse everywhere
  • Queens data is coming from Lucas — placeholder for now
  • Uses shared/style.css

Checklist

  • Toggle added
  • Queens placeholder
  • Lucas phone review
  • Queens data added when available
  • westside-playground-overhaul
### Type Feature ### Lineage Part of public site evolution. Parent note: `westside-playground-overhaul` ### Repo `forgejo_admin/westside-playground` ### User 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.html` has 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 - [ ] Kings/Queens toggle at top of page - [ ] Kings shows current 5 teams with schedules - [ ] Queens shows placeholder (TBD — data coming) - [ ] Same toggle pattern as Tryouts and Teams pages - [ ] Consistent toggle UX across all 3 toggled pages ### Test Expectations - [ ] Toggle switches content - [ ] All links resolve - [ ] Visual on 390px ### Constraints - Same toggle JS pattern — add to `shared/app.js` once, reuse everywhere - Queens data is coming from Lucas — placeholder for now - Uses `shared/style.css` ### Checklist - [ ] Toggle added - [ ] Queens placeholder - [ ] Lucas phone review - [ ] Queens data added when available ### Related - `westside-playground-overhaul`
Author
Owner

Scope Review: NEEDS_REFINEMENT

Review note: review-410-2026-03-25
Three fixable issues found before this ticket is agent-ready.

  • Repo mismatch: Issue filed on westside-app but ### Repo field says westside-playground and file target schedule.html only exists in westside-playground
  • Undocumented dependency: Scope references "Same toggle pattern as Tryouts and Teams pages" but neither tryouts.html (#92) nor teams.html (#93) exist yet. #92 is the ticket that creates the toggle pattern — this ticket depends on it but doesn't document that
  • Untestable acceptance criteria: "Consistent toggle UX across all 3 toggled pages" cannot be verified until #92 and #93 are complete
## Scope Review: NEEDS_REFINEMENT Review note: `review-410-2026-03-25` Three fixable issues found before this ticket is agent-ready. - **Repo mismatch:** Issue filed on `westside-app` but `### Repo` field says `westside-playground` and file target `schedule.html` only exists in `westside-playground` - **Undocumented dependency:** Scope references "Same toggle pattern as Tryouts and Teams pages" but neither `tryouts.html` (#92) nor `teams.html` (#93) exist yet. #92 is the ticket that creates the toggle pattern — this ticket depends on it but doesn't document that - **Untestable acceptance criteria:** "Consistent toggle UX across all 3 toggled pages" cannot be verified until #92 and #93 are complete
Author
Owner

Refinements from review-410-2026-03-25:

  1. Repo convention: Documented.

  2. Depends on #92 (Tryouts). #92 creates the Kings/Queens toggle foundation. This ticket reuses the pattern — same initKQToggle() JS, same .queens-active CSS, same localStorage persistence. Adding depends:ws-92.

  3. 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.

  4. No nav changes needed. Schedule already exists in the nav. This ticket only adds the toggle within the page.

**Refinements from review-410-2026-03-25:** 1. **Repo convention:** Documented. 2. **Depends on #92 (Tryouts).** #92 creates the Kings/Queens toggle foundation. This ticket reuses the pattern — same `initKQToggle()` JS, same `.queens-active` CSS, same localStorage persistence. Adding `depends:ws-92`. 3. **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. 4. **No nav changes needed.** Schedule already exists in the nav. This ticket only adds the toggle within the page.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo_admin/westside-landing#95
No description provided.