Application exhibit · Built for aiEDU
How Curriculum Studio was built
A CMS prototype demonstrating how aiEDU could evolve beyond its current static resource portal — with search, structured metadata, and a lightweight admin workflow.
Download video · Catalog search, collection, admin workflow, and AI metadata assist
Educators looking for AI-literacy classroom material currently navigate aiEDU's marketing site: resources are scattered across blog posts, PDFs, and standalone pages with no unified catalog, no search, no filtering by grade or time, and no metadata.
Internally, the Programs team manages curriculum by editing a website — no draft workflow, no visibility into what's used. Curriculum Studio prototypes the fix: one structured catalog for educators, one lightweight admin for the team.
| Feature | Status | Notes |
|---|---|---|
| Educator catalog + search/filters | Built | URL-synced filters, published-only view |
| My Collection | Mocked | localStorage; production = Google for Education SSO |
| Admin CRUD + status workflow | Built | draft → in-review → published |
| Data persistence | Mocked | localStorage overlay on JSON seed |
| Admin auth | Mocked | Demo passcode; production = RBAC |
| AI metadata generation | Mocked | Keyword-based; human-in-the-loop apply step |
| Analytics dashboard | Mocked | Seed view/download counts |
| Download / Launch links | Mocked | Toast placeholder for external assets |
- Can an educator find a relevant resource in under 60 seconds?
- Does the admin workflow support draft → review → publish?
- Does AI metadata assist reduce tagging effort without removing human review?
- Is the demo honest about what's production-ready vs. prototyped?
- Would this integrate with aiEDU's existing content ops (spreadsheets, Airtable)?
Interview Programs team on their Airtable/spreadsheet workflow and map fields to the Resource schema. Pilot CSV import (Phase 2) with their actual column names.
Shadow educators searching for materials today; validate filter dimensions and whether "duration" or "implementation model" matters more than topic tags.
Replace passcode auth with Google for Education SSO and role-based access (viewer / editor / publisher). Move persistence to Postgres via Supabase.
Connect real LLM metadata generation with structured output and audit logs for compliance review.
Full product requirements document: PRD.md in the repository root.
Built with Cursor + Claude. Estimated build time: ~10 hours (Phase 1).