feat(admin): deliver Phase 4 platform administration experience#145
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implemented Phase 4 of the EchoEd UI/UX overhaul: the Platform Admin experience.
Changes include:
Canonical guarded routes under /admin.
Admin overview with supported attention states, platform counts, shortcuts, and partial-failure
handling.
Privacy-conscious user directory, filtering, user details, role changes, and supported deletion
actions.
Read-only organization oversight based on existing API scope.
Course oversight separated from Content Studio authoring.
Badge catalog and supported badge creation/upload.
Platform reporting using existing analytics data.
Responsive administrative tables and mobile data-list alternatives.
Accessible confirmation flows for destructive and privilege-changing actions.
Admin and compatible super_admin navigation behavior.
Seeded Admin Playwright coverage.
Admin production, privacy, accessibility, API-contract, and backend-gap documentation.
Backend repair for UUID user detail/update requests.
Backend route-order repair preventing /api/users/students from being shadowed by /api/users/
{user_id}.
Motivation
Platform administrators needed a clear, trustworthy operational area for understanding users, roles,
organizations, courses, badges, and supported platform status.
The previous experience did not clearly distinguish platform oversight from teacher workflows,
Content Studio authoring, or organization-admin self-service. It also lacked consistent responsive
behavior, privacy-conscious information presentation, and clear handling of unsupported
administrative capabilities.
The backend repair was required because UUID-based user detail requests returned HTTP 500 in the
supported SQLite browser environment, blocking the Admin user-detail workflow.
Type of Change
Test Plan
List the checks you ran.
If you could not run a check, explain why:
Screenshots
Add screenshots for visible UI changes.
Accessibility Check
Community or Curriculum Impact
This change does not modify curriculum content, historical claims, source quality, educator review
behavior, or community contribution flows.
Course information is presented for platform oversight only. The Admin area does not add Content
Studio authoring or publishing controls.
Unsupported moderation capabilities remain hidden because the existing APIs do not provide
authenticated, safely scoped moderation behavior.
Learner-sensitive information is omitted from broad Admin lists, and organization visibility remains
constrained by current backend authorization.
Notes
Existing legacy Admin routes remain available through guarded aliases or redirects.
super_admin is treated according to verified backend behavior and is not assumed to inherit all
admin capabilities.
The backend change is limited to UUID route typing and static route ordering. It adds no endpoint,
migration, schema, JWT, or seed behavior.
Platform-wide organization oversight, account suspension, badge lifecycle management, moderation
queues, audit logs, and final-administrator protections remain documented backend gaps.
Dedicated privacy-minimized user API response schemas remain future work.
The Platform Admin production phase is complete. The full EchoEd UI/UX overhaul is not complete.