Creator Hub
Competitions and Creator Events
Creator events can drive seasonal packs, community voting, featured drops, and reward paths while keeping rules and judging visible.
Public surface
Competitions and Creator Events
Competitions should be fun but structured: clear themes, deadlines, ownership rules, review process, voting guardrails, prizes, and public winners.
Seasonal prompts, device constraints, style tags, and pack requirements.
Ownership, previews, package report, compatibility, and deadline requirements.
Public voting should avoid spam, manipulation, private data leaks, and unclear results.
Featured creators, badges, store shelves, and announcement copy.
| Event fields | Theme, dates, eligible packs, judging criteria, prizes, winners, and moderation notes. |
|---|---|
| Eligibility | Only creator-owned or properly licensed work should enter. |
| Review | Unsafe, broken, misleading, or infringing packs should be rejected before voting/showcase. |
| Rewards | Badges, featured shelf placement, credits, or community recognition should be clear and auditable. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
Publish theme, rules, dates, and pack requirements.
Creators upload review-ready entries.
Admin checks package quality and ownership.
Publish winners, badges, and featured shelves.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.