Skip to content

Web UI design, v1

The design lives in Doop, not in this repository: ExtractIt — UI v1 (11 frames, light and dark tokens, plus the brief pinned as the style guide extractit-ui). This page records what the design takes from public competitor material, the principles behind it, the token values and which ticket builds each screen.

Status: draft, not yet approved in Doop (approvalStatus: draft on every frame).

Screens

# Frame What it shows Ticket
0 Tokens y componentes Colour, type, buttons, badges, confidence bars, field row and evidence marks in light and dark T18
1 Inicio Four KPIs (awaiting review, processed in 7 days with STP, failed runs, production accuracy with n), recent activity with per-node progress, review queues with SLA, usage this period T18, T33, T40, T51
2 Documentos Drop zone with URL import and target workflow and version, status tabs with counts, filter chips, run table (status, total, minimum confidence, validation, reviewer), retry from the failed step, bulk bar T17, T18, T36
3 Visor de evidencias Page on the left with a box on each field's words; fields on the right with confidence; the selected field shows its verified quote, an alternative candidate, accept, correct and absent actions, and the failing blocking rule with a fix action; keyboard hints T18, T32
4 Bandeja de revisión Views, reasons and workflows as queues; reviewer metrics; tasks with reason, fields to review, assignee, SLA countdown; the active policy, double review and SLA escalation stated in plain words T33
5 Studio — lienzo Workflow header tabs, draft-of-version selector, warnings, Diff, Test, Publish; operator palette; typed graph (input → parse → classify → extract → validate → if/else → webhook or human review) with branch labels; config panel for the selected node (tier, schema summary, citations, lookup, last test) T34, T36
6 Editor de esquema Field tree (name, type, required, model description, rule count) with nested objects, tables and computed fields; inline detail with "improve with the agent"; Visual / JSON Schema toggle; live preview on a sample document with its evidence and dataset accuracy T35
7 Workflows Alias → version, documents in 30 days, accuracy with sparkline, STP, cost per page, last run, owner; templates T34
8 Miembros y roles Settings sub-navigation, members with role selector and project scope, pending invitation, the six roles explained T13
9 Uso y plan Pages against quota with month-end projection, plan, top-up credits, daily usage with projection, breakdown by workflow, budgets with alert and block thresholds T51
10 Claves API Keys with project, scopes, expiry and last use; the "shown once" dialog with a copy button and a curl example T12

Not designed yet: Health (datasets, evaluations, optimizer: T37/T38/T41), Monitoring (T40 has only the Inicio KPIs), Knowledge (T48), agent sessions, webhooks and connectors settings, login, empty and error states.

What we took from public material

Only public pages were read; no account was created and nothing was signed in to. Brand, logos, colours and copy of these products are not reused.

Product What it does well (public source) What the design takes
Anyformat Per-field confidence shown as a percentage, citations with click-through to the page position, composable graph with branching, chat assistant that builds a workflow; per-workflow tabs, version selector, keyboard verification (as recorded in research/08 part A) (site) Workflow header tabs; three-area Studio (palette, canvas, panel); keyboard-first review (⇧⏎ approve and next)
Extend Reviewer "snaps to the relevant page, highlights the coordinates and explains why"; reasoning for inferred values; a reusable bounding-box citation viewer in its MIT UI kit (citations and reasoning, UI kit, bounding boxes docs) The evidence card under the selected field (citation status, quote, alternative candidate); the viewer as one component reusable by T45
LlamaCloud (LlamaExtract) Document on the left, configuration on the right; Builder and JSON tabs kept in sync; every job stores the config it ran with (web UI guide) Visual / JSON Schema toggle in the schema editor; every run shows its workflow version
Rossum Documents needing review land in a "To review" queue; flagged fields must be fixed before export; after confirming, move to the next document (validation screen, now redirected to Coupa's docs) Review inbox as queues; blocking rules stop approval; "approve and next" as the primary action
Sensible Extraction config as editable cards; plain-language "quick edit" that proposes a JSON diff to accept or reject (visual editor) "Improve with the agent" on a field description and the agent hint on the canvas, both meant to return a reviewable diff
Reducto Studio Every run saved, configs compared side by side, per-field accuracy against eval data (Launch HN) "Re-run with another version" in the bulk bar; dataset accuracy beside the schema preview

Docsumo, Nanonets, Unstructured and Instabase: the public pages found describe integrations and comparisons, not their screens, so nothing was taken from them.

The gaps no one documents publicly, and where this design commits: a real runs table, the review inbox with SLA and double review, the workflow list, keyboard shortcuts shown in the UI, and word-level evidence boxes (competitors box the block).

Principles

  1. The document is the centre. Any value reaches its words on the page in one click; the selected field's box is the only strong colour on the page.
  2. Colour means something. One accent (ink blue) for selection, focus and evidence. Green, amber and red only for confidence and status. Neutral everywhere else.
  3. Say the policy out loud. Confidence is a number with a band from the active policy; the inbox states why a task exists and when it escalates; counts carry n.
  4. Calm density. One sidebar (it folds to a 56 px rail on the viewer, Studio and schema editor), 52 px top bar, 48–56 px table rows, generous gaps between groups and tight ones inside them.
  5. Keyboard first where people work in volume. Shortcuts are shown next to the actions that have them.
  6. Safe changes. Studio always edits a draft of a version; publishing is explicit.

Tokens

Defined on the Doop canvas (export with get_tokens as CSS or a Tailwind v4 @theme block). Names follow the shadcn/ui variables so T18 can map them one to one.

Token Light Dark Use
--color-background #F6F6F4 #0E0E10 App ground
--color-card #FFFFFF #161619 Cards, tables, panels
--color-sidebar #EFEFEC #121214 Sidebar and rail
--color-muted #F0F0EE #1E1E22 Table header, hover, neutral chips
--color-border #E4E4E0 #2A2A2F 1 px dividers
--color-border-strong #D2D2CC #3A3A40 Inputs and controls
--color-foreground #18181B #EDEDEF Text
--color-muted-foreground #6B6B70 #9A9AA2 Secondary text
--color-faint-foreground #9C9CA1 #6E6E76 Placeholders, metadata
--color-primary / -foreground #18181B / #FFFFFF #EDEDEF / #0E0E10 Primary button
--color-ink #3147D4 #8A98FF The accent: selection, focus ring, evidence, links
--color-ink-soft #E9ECFC #1E2347 Selected row or field
--color-evidence rgba(49,71,212,.16) rgba(138,152,255,.24) Fill of the selected evidence box
--color-success / -soft #1E7F4F / #E4F3EA #4CC38A / #16291F High confidence, approved, rule passed
--color-warning / -soft #A8620A / #FBF0DC #F0A94B / #2D2312 Medium confidence, needs review
--color-danger / -soft #C2362F / #FBE7E5 #F2766E / #331816 Low confidence, failed, blocking rule, contradiction
Type Value
--font-sans Geist 400/500/600: UI and body, 14 px base, 13 px tables, 12 px labels
--font-display Instrument Serif 400: page H1 (32 px) and KPI figures only
--font-mono Geist Mono: extracted values, amounts, IDs, code
Radius --radius-sm 6 px (chips), --radius-md 8 px (buttons, inputs), --radius-lg 12 px (cards)
Spacing 4, 8, 12, 16, 24, 32 px (--spacing-1 … --spacing-8)
Shadows None on cards; only popovers, dialogs, the bulk bar and the document page

All three fonts are under the SIL Open Font License; self-host them rather than loading Google Fonts.

Notes for implementation

  • Components map to shadcn/ui on Base UI: Button, Badge, Card, Table (TanStack), Tabs, Select, Switch, Dialog, Sheet, Command (⌘K), Tooltip, Toggle Group (tier and view switches).
  • Icons are Lucide; each mockup element carries the icon name in data-i. Use lucide-react.
  • The frames load icons with a small inline script and CSS masks to work around the Doop renderer. Do not copy that into web/.
  • The page in the viewer stays white in dark mode; only the chrome changes.
  • Evidence marks: selected = --color-evidence fill plus a 2 px --color-ink outline and a label with the field and confidence; other fields = 1 px dashed ink outline; contradiction or not extracted = red outline.
  • Confidence bar: 28 × 4 px track, fill width = value, colour from the policy band, value in mono with a decimal comma in Spanish.