NickFitton / NickFitton/FortSprite
Decide Chapter Season catalogue ordering semantics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Question
What deterministic ordering rules should the Override catalogue use for Chapter Seasons, Sprites, and Variant definitions in the player season hub and administration back office? Decide whether administrators control any ordering, how historical content is ordered, and how the chosen rules remain stable as entries are released or archived.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The affected entry points named are the player season hub and administration back office, covering Chapter Seasons, Sprites, and Variant definitions. Start by tracing how these catalogue entries are currently represented and displayed in both areas. Done means the ordering rules, administrator control, historical-content behavior, and release/archive stability are explicitly decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100