design / dashboard rework

Dashboard direction mockups

Three genuinely divergent directions for the moderation dashboard, built as static clickdummies. Every one depicts the identical shared scenario, so they can be compared head-to-head.

Shared scenario Lumen · en → de / fr / ja ·1,243 pending·312 keys·38 new today·hero.title 5-way de contest·47-key long tail·22-suggestion ja burst·coverage de 94% / fr 71% / ja 22%
direction 1 1

Verdicts

decision inbox

The queue is not a list of suggestions; it is a router. Every key+locale group is classified by the shape of the decision it requires and delivered to a stream where one keystroke completes it. You never browse. You burn down.

What is a row?
A decision — a key+locale group routed by type: Ready, Pick a winner, Scrutiny, Incident, Coverage.
Open mockupverdicts.html
direction 2 2

Stringbook

locale-grid catalog

The project IS a key × locale matrix. There is no queue — pending work is a cell state inside the catalog, the way a dirty file is a state inside a file tree. Moderation is walking the matrix and emptying hot cells.

What is a row?
A string — one key across all locale columns; pending work is a cell state, coverage is the column header.
Open mockupstringbook.html
direction 3 3

Showdown

ranked contest player

There is no list. The screen IS one key+locale contest at a time, and Enter publishes-and-advances through a ranked finite run. The queue is a lobby of launchable runs, never rows. You don't browse moderation work; you play it.

What is a row?
There isn't one — a full-bleed contest card replaces the row; the overview is a lobby of runs.
Open mockupshowdown.html
clickdummy