docs(#240): Mission Control Strip spec — dashboard expansion design decision #244

marcel · 2026-04-15T22:53:14+02:00

marcel commented

2026-04-15 22:53:14 +02:00

Summary

Adds docs/specs/dashboard-expansion-patterns.html — four pattern alternatives evaluated (Tabs, Accordion, Mission Control, Priority Queue) with annotated desktop + mobile mockups, engagement feature proposals, and the final recommendation
Adds docs/specs/mission-control-strip-final.html — clean implementation blueprint: pipeline diagram, column definitions, sorting strategy (seeded weekly shuffle + expert flag), full Tailwind impl-ref table, backend contracts, and new component list

Design Decision

Chosen pattern: Mission Control Strip — a full-width 3-column section below the existing grid, outside the existing right column, so nothing gets pushed below the fold.

Three columns mapping to the transcription pipeline:

Segmentierung — docs with annotation_count = 0; no skill needed, anyone can draw boxes
Transkription — docs with annotation_count > 0 and reviewed_pct < 0.90; per-document mini progress bar
Lesefertig — docs with reviewed_pct ≥ 0.90; branded mint background, percentage text

Sorting: ORDER BY textedBlocks DESC, HASHTEXT(id || week) — partial progress surfaces first, zero-progress rotates weekly so buried easy documents get a chance.

Expert flag escape hatch: PATCH /api/documents/{id}/needs-expert marks illegible documents with a purple badge and sorts them after unflagged docs — prevents hard Kurrent pages from monopolising the column indefinitely.

Progress granularity: Weekly pulse (↑ +5 diese Woche) for column headers avoids the cold-start demotivation of a 0.8% global bar on 1 500 documents; per-document bars only when annotation_count > 0.

Closes #240 (spec phase)

🤖 Generated with Claude Code

## Summary - Adds `docs/specs/dashboard-expansion-patterns.html` — four pattern alternatives evaluated (Tabs, Accordion, Mission Control, Priority Queue) with annotated desktop + mobile mockups, engagement feature proposals, and the final recommendation - Adds `docs/specs/mission-control-strip-final.html` — clean implementation blueprint: pipeline diagram, column definitions, sorting strategy (seeded weekly shuffle + expert flag), full Tailwind impl-ref table, backend contracts, and new component list ## Design Decision **Chosen pattern: Mission Control Strip** — a full-width 3-column section below the existing grid, outside the existing right column, so nothing gets pushed below the fold. **Three columns mapping to the transcription pipeline:** 1. **Segmentierung** — docs with `annotation_count = 0`; no skill needed, anyone can draw boxes 2. **Transkription** — docs with `annotation_count > 0` and `reviewed_pct < 0.90`; per-document mini progress bar 3. **Lesefertig** — docs with `reviewed_pct ≥ 0.90`; branded mint background, percentage text **Sorting:** `ORDER BY textedBlocks DESC, HASHTEXT(id || week)` — partial progress surfaces first, zero-progress rotates weekly so buried easy documents get a chance. **Expert flag escape hatch:** `PATCH /api/documents/{id}/needs-expert` marks illegible documents with a purple badge and sorts them after unflagged docs — prevents hard Kurrent pages from monopolising the column indefinitely. **Progress granularity:** Weekly pulse (`↑ +5 diese Woche`) for column headers avoids the cold-start demotivation of a 0.8% global bar on 1 500 documents; per-document bars only when `annotation_count > 0`. Closes #240 (spec phase) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

marcel added 1 commit 2026-04-15 22:53:14 +02:00

docs(#240 ): add Mission Control Strip spec and pattern alternatives

CI / Unit & Component Tests (push) Failing after 2m25s

Details

CI / Backend Unit Tests (push) Failing after 2m38s

Details

CI / Unit & Component Tests (pull_request) Failing after 2m11s

Details

CI / Backend Unit Tests (pull_request) Failing after 8h41m14s

Details

5bd7f0d486

Adds the design decision record for how to expand the dashboard without
pushing content below the fold: a full-width 3-column strip (Segmentierung /
Transkription / Lesefertig) below the existing grid.

- dashboard-expansion-patterns.html — four pattern alternatives evaluated
  (Tabs, Accordion, Mission Control, Priority Queue) with annotated mockups,
  engagement feature proposal, and final recommendation.
- mission-control-strip-final.html — clean implementation blueprint with
  pipeline diagram, column definitions, seeded-weekly-shuffle sorting,
  expert-flag escape hatch, all Tailwind impl-ref values, and backend
  contracts.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

marcel referenced this pull request

2026-04-15 22:53:37 +02:00

As a family member I want to see which documents need transcription and which are ready to read so I know where to contribute #240

marcel referenced this pull request

2026-04-16 07:58:53 +02:00

feat(#240): Mission Control Strip — backend + frontend implementation #245

marcel closed this pull request

2026-04-16 09:09:55 +02:00

CI / Unit & Component Tests (push) Failing after 2m25s

Details

CI / Backend Unit Tests (push) Failing after 2m38s

Details