What exists now
- Seasonal competition structure with explicit stage windows.
- School, band, and student role boundaries.
- Editorial content and public celebration outputs for the client team.
Client platform rationale
Why schools use challenge ME
The product is designed around school-admin workflows rather than generic course-platform assumptions.
Why rebuild
The current site validates the business model, but it mixes content, LMS logic, reporting, and payments inside a plugin stack.
What improves
- Explicit domain entities for seasons, stages, schools, quests, and payments.
- Cleaner role boundaries between admins, coordinators, band leaders, and students.
- A headless content model that can evolve without touching competition logic.
Roles in contrast
The rebuild keeps the live roles but removes the current overlap between school-level and band-level permissions.
platform admin
Owns season setup, school approval, content publishing, and stage operations.
- Approve teacher registrations and assign school coordinators.
- Configure seasons, stages, quest windows, and advancement rules.
- Publish celebration stories and seasonal content.
school coordinator
Owns the school account and operational setup.
- Manage school profile, active bands, and seat capacity.
- Assign or remove band leaders.
- Oversee payments and stage-seat fulfillment.
band leader
Runs the cohort day to day.
- Create, import, edit, and archive students.
- Monitor participation, quest progress, and integrity reviews.
- Send welcome emails and broadcast updates to students.
student
Completes quests and tracks personal progress.
- Access staged competition routes and timed quests.
- Review learn content and message feed.
- Track progress, scores, and next competition steps.