Add admin UX improvement epic with 8 child feature beans
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
---
|
||||
# nuzlocke-tracker-9cx2
|
||||
title: Drag-and-drop reordering for boss battles
|
||||
status: todo
|
||||
type: feature
|
||||
created_at: 2026-02-08T12:33:18Z
|
||||
updated_at: 2026-02-08T12:33:18Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Add drag-and-drop reordering for boss battles, matching the existing pattern used for routes.
|
||||
|
||||
## Current behavior
|
||||
- Boss battles have a manual 'order' field that must be edited individually
|
||||
- Routes already have drag-and-drop reordering via @dnd-kit
|
||||
|
||||
## Desired behavior
|
||||
- Boss battles in the AdminGameDetail bosses tab support drag-and-drop reordering
|
||||
- Same visual pattern as routes: drag handle on the left, auto-recalculate order on drop
|
||||
- Reuse the same @dnd-kit setup already in place for routes
|
||||
|
||||
## Files
|
||||
- frontend/src/pages/admin/AdminGameDetail.tsx — add DnD to bosses tab
|
||||
- Backend may need a reorder endpoint for bosses (similar to routes reorder)
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
# nuzlocke-tracker-dyzh
|
||||
title: Click-to-edit pattern across admin tables
|
||||
status: todo
|
||||
type: feature
|
||||
priority: high
|
||||
created_at: 2026-02-08T12:32:53Z
|
||||
updated_at: 2026-02-08T12:35:03Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
blocking:
|
||||
- nuzlocke-tracker-fxi7
|
||||
- nuzlocke-tracker-mg46
|
||||
---
|
||||
|
||||
Replace the current pattern of separate Edit/Delete action buttons with an inline click-to-edit pattern across all admin pages.
|
||||
|
||||
## Current behavior
|
||||
- Table rows show data with Edit and Delete buttons on the right
|
||||
- Clicking Edit opens a modal form
|
||||
- Clicking Delete opens a confirmation dialog
|
||||
|
||||
## Desired behavior
|
||||
- Clicking a table row opens an edit card/panel inline or as a detail view
|
||||
- The edit card shows all fields in editable form
|
||||
- A Delete button is available within the edit card
|
||||
- Save/Cancel buttons to confirm or discard changes
|
||||
- Clicking outside or pressing Escape cancels
|
||||
|
||||
## Affected pages
|
||||
- AdminPokemon (pokemon table)
|
||||
- AdminEvolutions (evolutions table)
|
||||
- AdminGames (games table)
|
||||
- AdminGameDetail routes tab (routes table)
|
||||
- AdminGameDetail bosses tab (boss battles table)
|
||||
- AdminRouteDetail (route encounters table)
|
||||
- AdminRuns (runs table — delete only, no edit)
|
||||
|
||||
## Notes
|
||||
- Some pages already have row click handlers (Games navigates to detail). Preserve that where it makes sense — the edit card could be the detail page itself.
|
||||
- Keep modal forms for Create (adding new entities) since there's no row to click yet.
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
# nuzlocke-tracker-em40
|
||||
title: Add filtering to admin tables
|
||||
status: todo
|
||||
type: feature
|
||||
priority: low
|
||||
created_at: 2026-02-08T12:33:46Z
|
||||
updated_at: 2026-02-08T12:33:46Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Add filter controls to admin tables beyond the existing text search.
|
||||
|
||||
## Current state
|
||||
- Pokemon and Evolutions have text search
|
||||
- No other filter dimensions available
|
||||
|
||||
## Desired filters
|
||||
- **Pokemon**: Filter by type, generation (derived from dex range)
|
||||
- **Evolutions**: Filter by trigger type (level-up, trade, item, etc.)
|
||||
- **Games**: Filter by region, generation
|
||||
- **Routes**: Filter by encounter method availability
|
||||
- **Runs**: Filter by status (active, completed, failed), game
|
||||
|
||||
## UX
|
||||
- Filter chips or dropdown selectors above the table, next to the existing search bar
|
||||
- Filters combine with search (AND logic)
|
||||
- Clear all filters button
|
||||
@@ -0,0 +1,27 @@
|
||||
---
|
||||
# nuzlocke-tracker-fxi7
|
||||
title: Pokemon detail card with encounters and evolution chain
|
||||
status: todo
|
||||
type: feature
|
||||
priority: high
|
||||
created_at: 2026-02-08T12:33:05Z
|
||||
updated_at: 2026-02-08T12:33:05Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
When viewing/editing a Pokemon in the admin panel, show contextual information about where it can be encountered and its evolution chain.
|
||||
|
||||
## Desired behavior
|
||||
- The pokemon edit card (from click-to-edit) shows:
|
||||
1. Editable fields (name, types, dex number, sprite, etc.)
|
||||
2. **Encounter locations**: A list of routes/games where this pokemon appears as a route encounter. Grouped by game, showing route name + encounter method + levels.
|
||||
3. **Evolution chain**: Visual display of the pokemon's evolution family — predecessors and successors with triggers (level, item, trade, etc.)
|
||||
- Encounter locations and evolution chain are read-only informational sections
|
||||
- Encounter locations link to the route detail page in admin for quick navigation
|
||||
|
||||
## Backend support
|
||||
- Encounters by pokemon: May need a new endpoint or can query route_encounters filtered by pokemon_id
|
||||
- Evolution chain: Can reuse existing /pokemon/{id}/evolutions endpoint, but may need a 'full chain' variant that shows the complete family tree (not just direct evolutions from this pokemon)
|
||||
|
||||
## Notes
|
||||
- This helps the admin quickly verify data completeness — 'is this pokemon assigned to the right routes?' and 'are its evolutions set up correctly?'
|
||||
17
.beans/nuzlocke-tracker-iu5b--admin-ux-improvement-round.md
Normal file
17
.beans/nuzlocke-tracker-iu5b--admin-ux-improvement-round.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
# nuzlocke-tracker-iu5b
|
||||
title: Admin UX improvement round
|
||||
status: in-progress
|
||||
type: epic
|
||||
created_at: 2026-02-08T12:32:43Z
|
||||
updated_at: 2026-02-08T12:32:43Z
|
||||
---
|
||||
|
||||
A round of UX improvements to the admin panel to make data editing more intuitive and efficient. The admin panel is the primary tool for populating game data (routes, encounters, bosses, evolutions), so friction here directly slows down adding support for new games.
|
||||
|
||||
## Key themes
|
||||
|
||||
- **Consistency**: Unify interaction patterns across all admin pages (click-to-edit, reordering, selectors)
|
||||
- **Efficiency**: Reduce clicks and navigation depth for common workflows
|
||||
- **Discoverability**: Surface related data (where a pokemon appears, its evolution chain) directly in context
|
||||
- **Bulk operations**: Enable importing all entity types, not just Pokemon
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
# nuzlocke-tracker-kghn
|
||||
title: Child route management from route detail
|
||||
status: todo
|
||||
type: feature
|
||||
priority: low
|
||||
created_at: 2026-02-08T12:33:53Z
|
||||
updated_at: 2026-02-08T12:33:53Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Allow adding/editing/deleting child routes (sub-areas) directly from the route detail page, instead of only from the game detail routes tab.
|
||||
|
||||
## Current state
|
||||
- Child routes can only be created from the game detail routes tab
|
||||
- The route detail page shows encounters but doesn't show or manage its children
|
||||
- To add a child route, you navigate away from the route detail back to the game
|
||||
|
||||
## Desired behavior
|
||||
- Route detail page shows a 'Sub-areas' section listing child routes (if any)
|
||||
- Can add new child routes from this view
|
||||
- Can click a child route to navigate to its encounter detail
|
||||
- Can delete child routes from this view
|
||||
|
||||
## Notes
|
||||
- This is lower priority since child routes are typically set up once during initial data entry and rarely changed afterward.
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
# nuzlocke-tracker-ljle
|
||||
title: Route navigation within game detail
|
||||
status: todo
|
||||
type: feature
|
||||
created_at: 2026-02-08T12:33:26Z
|
||||
updated_at: 2026-02-08T12:33:26Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Reduce navigation depth when working with route encounters. Currently requires: Games > Game > Routes tab > Click route, and there's no way to jump between sibling routes.
|
||||
|
||||
## Desired behavior
|
||||
- On the route detail page (AdminRouteDetail), add prev/next route navigation buttons to quickly move between routes in the same game
|
||||
- Consider showing a sidebar or dropdown with all routes for quick jumping
|
||||
- Breadcrumbs should be clickable to go back to the game detail
|
||||
|
||||
## Notes
|
||||
- The route order is already available — sort by order to determine prev/next
|
||||
- This is particularly useful when populating encounter data for a new game, going route by route
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
# nuzlocke-tracker-mg46
|
||||
title: Use PokemonSelector autocomplete for route encounters
|
||||
status: todo
|
||||
type: feature
|
||||
created_at: 2026-02-08T12:33:11Z
|
||||
updated_at: 2026-02-08T12:33:11Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Replace the basic <select> dropdown in the route encounter form (AdminRouteDetail) with the PokemonSelector autocomplete component already used in the boss team editor.
|
||||
|
||||
## Current behavior
|
||||
- Route encounter form has a plain HTML select dropdown listing all pokemon
|
||||
- Difficult to find a specific pokemon in a list of 1000+
|
||||
|
||||
## Desired behavior
|
||||
- Use the existing PokemonSelector component (autocomplete with search, sprite preview, dex number)
|
||||
- Same UX as the boss team editor pokemon selection
|
||||
|
||||
## Files
|
||||
- frontend/src/pages/admin/AdminRouteDetail.tsx — update the form
|
||||
- frontend/src/components/admin/RouteEncounterFormModal.tsx — replace select with PokemonSelector
|
||||
@@ -0,0 +1,28 @@
|
||||
---
|
||||
# nuzlocke-tracker-ok1t
|
||||
title: Bulk import for evolutions, routes, and bosses
|
||||
status: todo
|
||||
type: feature
|
||||
created_at: 2026-02-08T12:33:39Z
|
||||
updated_at: 2026-02-08T12:33:39Z
|
||||
parent: nuzlocke-tracker-iu5b
|
||||
---
|
||||
|
||||
Extend the bulk import capability (currently Pokemon-only) to cover evolutions, routes, and boss battles.
|
||||
|
||||
## Current state
|
||||
- Pokemon has a bulk import modal that accepts JSON and reports created/updated/errors
|
||||
- Evolutions, routes, and bosses can only be created one at a time
|
||||
- All entities can be exported to JSON
|
||||
|
||||
## Desired behavior
|
||||
- Add bulk import modals to:
|
||||
- AdminEvolutions — import evolutions JSON
|
||||
- AdminGameDetail routes tab — import routes JSON (with children/encounters)
|
||||
- AdminGameDetail bosses tab — import bosses JSON (with pokemon teams)
|
||||
- Import format should match the export format for round-trip compatibility
|
||||
- Show progress/results summary (created, updated, errors) like the Pokemon import
|
||||
|
||||
## Backend
|
||||
- May need new bulk-import endpoints for evolutions, routes, and bosses
|
||||
- Or extend existing seed loader functions to be callable via API
|
||||
Reference in New Issue
Block a user