Skip to content

Assessment: Rebuild UI/UX design #263

Description

@vprashrex

Is your feature request related to a problem?
The current /assessment module does not align with the approved UI/UX design, leading to confusion and inefficiencies for users navigating assessments.

Describe the solution you'd like
Rebuild the /assessment module to match the approved design and migrate it to the BATCH assessments API. Key changes include:

  • Home: Replace Datasets / Config / Result tabs with Assessors and Runs panels.
  • Wizard: Implement a streamlined 4-step flow with new entry modes.
  • Prompt editor: Add token highlighting, two-stage @-mentions, live preview, draggable split pane, and model picker.
  • Save: Enable versioning only on significant diffs.
  • Results: Provide a results table with modal details, CSV export, and polling for status.
  • API: Create new /api/assessment/batch routes and restructure fetchers.

Additionally, review notes highlight significant LOC reduction and necessary decisions on certain components.

Original issue

Rebuilds /assessment to match the approved design (docs/assessment-ui-ux-flow.md) and moves it onto the BATCH assessments API.

What changes

Home — replaces the Datasets / Config / Result tabs with two panels: Assessors (search, version chips, cursor pagination, delete) and Runs (filter by assessor/version, status, Export, View results). Selecting a version is the pivot that enables Edit and New run.

Wizard — one 4-step flow (Submission → Pre-filter → Assessment → Run) with three entry modes: new assessor, edit version, run existing. Column mapping is gone; text and attachment columns are derived from the prompt's @Column / <Column> tokens.

Prompt editor (steps 2–3) — two zones per step with token highlighting, two-stage @-mentions (pick column → pick Text/Image/PDF), a live preview filled with row 1, a draggable split pane and heading-anchored scroll sync. Model picker per step in the flow strip.

Save — Review & save writes a new version (vN+1), enabled only on a real diff against the loaded version; whitespace-only edits don't count.

Results — table with row-detail modal (scores + reasons, feedback, attachments), CSV export, and the existing spreadsheet view one click away. Polls until the run reaches a terminal status.

API — new /api/assessment/batch BFF routes; fetchers split into lib/assessment/api/{assessors,runs,submissions}.ts. Assessors are ASSESSMENT-tagged configs, so configBlob.ts maps between the wizard draft and the stored blob (input_schema carries attachment types both ways). batchResults.ts flattens the nested BATCH result into the wide row the table reads.

Notes for review

  • ~6.7k LOC deleted: the legacy wizard, the multi-config fan-out UI, and the old review sections. A run now targets one assessor version instead of 1–4 configs.
  • Duplicate detection is no longer configurable in the wizard; the stage still renders on a run.
  • PostProcessingPanel.tsx / PostProcessingStep.tsx are kept but currently unreachable — the 4-step flow has no place for them. Needs a call on whether to re-host or drop.

tsc, npm run lint and npm run build all clean.

Activity

  1. changed the title [-]Rebuild the Assessment module (UI/UX v2) on the BATCH API[/-] [+]Assessment: Rebuild UI/UX design[/+] on Sep 15, 2026
  2. self-assigned this
    on Sep 15, 2026
  3. changed the issue type fromtoon Sep 15, 2026
  4. moved this from To Do to In Progress in Kaapi-devon Sep 15, 2026
  5. moved this from In Progress to Closed in Kaapi-devon Sep 17, 2026
  6. closed this as completedby moving to Closed in Kaapi-devon Sep 17, 2026
  7. github-actions commented on Oct 6, 2026

    @github-actions

    🎉 This issue has been resolved in version 0.5.0-main.5 🎉

    The release is available on GitHub release

    Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

  • Status
    No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions