Built at ASU Fall Hackathon 2026 | Phoenix Hackathon for Nonprofits: Nov 14-15 for the public good (MIT license).
⚠️ This is your team's ONE repository — all code goes here. Please don't create another repo (personal or org). Judges, the Team Dashboard's code-activity card, the public project page and the nonprofit all read this repo; work pushed anywhere else is invisible to them and won't count. Everyone on the team should be a collaborator here — ask an organizer in Slack if someone can't push.
| Nonprofit | Coding in Color |
| Problem statement | Curriculum & Student Progress Platform (CIC Problem 1) |
| Team page | Code Titans · Team Dashboard (story, demo video, submit) |
| Slack | team: #codetitans · nonprofit: #npo-coding-in-color · help: #ask-a-mentor |
| Created by | Greg V [Staff/Mentor] |
Start recording your demo video by Sun Nov 15, 12:00 PM MST — hacking ends at Sun Nov 15, 2:00 PM MST, and a demo you recorded with time to spare beats a feature you finished at 1:59.
- Sun Nov 15, 11:00 AM MST — Presentation Feedback Hour
- Sun Nov 15, 12:00 PM MST — Start recording your demo video
- Sun Nov 15, 12:30 PM MST — Judges Arrive
- Sun Nov 15, 2:00 PM MST — 🛑 Submission Deadline: Hacking ends
- Sun Nov 15, 2:05 PM MST — Judging Round 1
- Sun Nov 15, 3:40 PM MST — Judging Final Round
- Sun Nov 15, 4:30 PM MST — Closing Ceremony: Winners Announced
Everything is submitted from your Team Dashboard; judges read the dashboard, this README and your demo video.
- Code pushed to this repo, in small PRs (see
AGENTS.md) — judges and future recruiters read the history - Project story written on the dashboard (
#project): the problem, who it helps, what you built, what's next - Demo video (4 minutes or less) on YouTube, Vimeo, Loom or Google Drive, linked on the dashboard (
#demo) — show it working, not slides - Submit on the dashboard (you can keep editing until the close)
- This README filled in below: team, tech stack, how to run it, live link if you have one
- Optional: a DevPost entry — the dashboard is the submission of record.
Judges score Scope, Documentation, Polish and Security, plus a separate Accessibility prize — the rubric is at ohack.dev/hackathon-judging-criteria. Document your work as GitHub Issues as you go: that's how you get public credit for it.
- Frontend: Next.js (App Router) + TypeScript, static export, Tailwind CSS (see
frontend/) - Backend:
- Database:
- APIs / services:
git clone https://github.com/2026-Arizona-Opportunity-Hack/Code Titans-CodinginColor.git
cd Code Titans-CodinginColor
cp .env.example .env # fill in your own values — never commit .env
# install + start commands hereNeeds Node 20 or newer. It runs on fake data (Mock Service Worker) until the backend is deployed.
cd frontend
cp .env.example .env.local # keep NEXT_PUBLIC_USE_MOCKS=true for fake data
npm install
npm run dev # http://localhost:3000With fake data on, the demo student is class code K7M4QX with secret words maple-tiger-blue. Open
http://localhost:3000/s/#K7M4QX.maple-tiger-blue to land signed in as Maya (students use a personal link, not an account).
Staff screens: open http://localhost:3000/login/ and pick a demo role (instructor, CIC admin or reviewer). Real staff
sign-in uses Cognito and is not connected yet.
Other commands: npm run lint, npm run typecheck, npm run build (static export to frontend/out/).
Only NEXT_PUBLIC_ values are exposed to the browser, so never put a secret in them.
- Live demo: https://main.d3voqx7r17ipz6.amplifyapp.com (staff sign in at /login, students at /s)
- Demo video:
- Design / docs:
Winning teams finish the project with the nonprofit — the Definition of Done (deployed, nonprofit sign-off, docs, open source) is tracked on your team page. Keep the repo public and the README honest; recruiters do read these.
Need a hand this weekend? #ask-a-mentor on Slack, or ask in #codetitans and a mentor will drop in.