Everything you need to understand, build, and grow the DoCurious educational challenge platform.
Understanding features, rules, and status?
Building features or fixing bugs?
Working on UI or design system?
Getting oriented with DoCurious?
| Feature | What It Does | Status |
|---|---|---|
| Challenges | Users discover and complete real-world challenges | Built |
| Track Records | Document and verify challenge completions | Built |
| Communities | Groups with bucket lists, track records, and discussions | Built |
| Gamification | XP, badges, levels, streaks, and learning paths | Built |
| School Tools | Admin → Teacher → Student → Parent hierarchy | Partial |
| Vendor Portal | Vendors create and manage challenge listings | Built |
| Safety & Moderation | Content reporting, blocking, and COPPA compliance | Built |
| i18n | English, Spanish, and French | Built |
Throughout the docs you'll see these badges indicating implementation progress:
| Badge | Meaning |
|---|---|
| Built | Fully implemented with UI and store integration |
| Partial | Core exists, some spec requirements use mock data |
| Planned | In the V2 spec but not yet implemented |
| Not Started | No implementation yet |
Overall progress: 142 done, 21 partial, 12 not started across 23 spec documents. Full breakdown →
| API Reference — auto-generated TypeScript docs | Route Map — all 195 app routes |
| Permissions Matrix — role × feature access | Store Reference — 30 Zustand stores |
| Infrastructure Costs — monthly projections | Product Roadmap — what's next |
