NickFitton / NickFitton/FortSprite

Wayfinder: Plan the Override chapter-season catalogue and administration

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wayfinder:map
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Destination

Produce an implementation-ready specification and sequenced engineering plan for making Chapter 7 Season 4: Override the default FortSprite catalogue, with persistent sign-in, role-gated sprite administration, remotely stored images, and an editable chapter-season sprite catalogue.

Notes

Planning only: do not implement within this map. Preserve the existing historical catalogue and its current behaviour. Use /grilling and /domain-modeling for human decisions; use /convex:convex-expert before any future changes under convex/.

Settled product direction: a Chapter Season is the catalogue boundary; one administrator-selected Chapter Season is current; variants have independent progress; unavailable content stays visible and locked; progress is scoped to a Chapter Season; administrators are Clerk users whose public metadata includes the sprite-admin role; images use Convex File Storage; entries with progress are archived rather than hard-deleted.

Decisions so far

Not yet specified

Out of scope

  • Implementing the new catalogue, administration portal, or storage integration.
  • Changing the existing historical catalogue or its current progress behaviour.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read issues 24, 27, 26, and 25 for the settled Clerk, Convex, catalogue, journey, and loading decisions. Review the existing historical catalogue and current progress behaviour, then use /grilling and /domain-modeling for any human decisions before consulting /convex:convex-expert for future work under convex/. Done is an implementation-ready specification and sequenced engineering plan, without implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, authorization, backend, database, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.