content studio changes for content admin

[mrwrite]

Summary

Implemented Phase 5 of the EchoEd Production UI/UX Overhaul for the supported content_admin Content Studio surface.

Changes include:

• Added canonical, role-guarded /studio/** routes.
• Added Studio overview, projects, content, courses, programs, sources, drafts, review, and publishing views.
• Added searchable and responsive content libraries.
• Added project-scoped source and draft creation.
• Added safe draft preview without learner enrollment, sessions, or progress mutations.
• Added confirmed review and publishing actions that wait for backend success.
• Updated role-aware navigation so content administrators land in Studio.
• Preserved existing /workspace/** routes and deep links.
• Added Studio unit and seeded Playwright coverage.
• Documented API contracts, route migration, accessibility, responsive behavior, governance, action risks, and verified backend gaps.
• Completed only the applicable Studio OpenSpec task.

Motivation

Content administrators needed a dedicated curriculum-focused experience that clearly separates editorial work from Platform Admin, Teacher, and Student workflows.

The new Studio experience makes supported content, sources, drafts, review states, visibility, and publishing actions easier to understand while keeping backend authorization authoritative. Unsupported
curriculum editing, uploads, approval workflows, and other incomplete capabilities are documented instead of being presented as unsafe or nonfunctional controls.

Type of Change

• Documentation
• Frontend
• Backend
• Tests
• Accessibility
• Demo
• Curriculum/community review
• Other

Test Plan

List the checks you ran.

• Backend tests
• Frontend build
• Frontend unit tests
• Demo smoke test
• Manual review
• Not run. Explain below.

Results:

• Frontend production build passed.
• Frontend unit tests passed: 256 SUCCESS.
• TypeScript application compilation passed.
• Playwright discovery passed: 5 tests across 3 files.
• Seeded Chromium smoke suite passed: 5 passed.
• Strict OpenSpec validation passed.
• Phase-specific git diff --check passed.
• Forbidden Studio terminology scan returned no matches.

If you could not run a check, explain why:

Backend tests were not rerun because this phase contains no backend changes. Seeded browser tests used a disposable SQLite database because local Docker and PostgreSQL were unavailable.

A full manual screen-reader, 200% zoom, user-override contrast, mobile virtual-keyboard, and long-citation review was not completed.

Screenshots

Attach Studio demo screenshots or video showing:

• Studio overview
• Projects and content libraries
• Source library
• Draft preview
• Review queue
• Publishing confirmation
• Mobile layout around 390px

Accessibility Check

The Studio pages use logical headings, labeled native controls, visible focus states, textual status labels, live status and error announcements, and shared accessible confirmation dialogs.

Review and publishing dialogs trap focus, support Escape, prevent duplicate submission, and restore focus after closing. Responsive records preserve information and actions without relying on desktop-only
tables or drag-only interactions. The seeded smoke test verifies keyboard focus and the absence of horizontal overflow at 390px.

Manual screen-reader timing, 200% zoom, user-override contrast, and mobile virtual-keyboard behavior remain follow-up review items.

Community or Curriculum Impact

This change improves the curriculum contribution and review flow for content administrators. It provides clearer visibility into content drafts, sources, review states, audience availability, and publishing
consequences.

Source handling remains limited to fields supported by the current API. The UI does not invent citation data, credibility scores, rights information, historical validation, or curriculum completeness scores.
Preview mode does not affect learner progress.

No Community experience, student runtime behavior, teacher workflow, or historical content was changed.

Notes

• No backend endpoints, database migrations, authentication behavior, authorization rules, or seed behavior changed.
• Existing /workspace/** routes remain available for compatibility.
• Full course, unit, lesson, activity, and assessment authoring remains deferred because content_admin does not have a coherent ownership-safe API surface.
• Asset uploads, bibliographic rights metadata, review comments, reviewer assignment, version history, collaborative editing, and reversible unpublishing remain documented backend gaps.
• Existing Sass deprecation and initial-bundle budget warnings remain.
• The Content Studio phase is complete for the currently supported content_admin surface. The full EchoEd UI/UX overhaul is not complete.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
echoed	Ready	Preview, Comment	Jul 14, 2026 1:55am