[Design] Redesign research components
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- bun, typescript
Direzione di ricerca
Start at /design-audit#authored-content and inspect the research composer and SidecarCard-based lifecycle cards in packages/editor. Use the stated lifecycle stages and acceptance criteria to create the lifecycle state matrix, then verify with bun run types, bun run ci, bun test packages/editor, and bun run e2e. Done includes Maggie-approved specimens, screenshots at normal and narrow widths, reduced-motion and keyboard evidence, and confirmation that identity and publication semantics are unchanged.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Base branch: main
Branch: maggie/redesign-research-components
Depends on: None
Goal
Redesign the complete research request family so entry, progress, failure, cancellation, and ready states feel like one polished workflow.
Context From Planning
- Every research component in
/design-audit#authored-contentcurrently feels underdesigned and needs a dedicated pass. - Research requests are inline durable cards, not standalone channels. Their identity survives failure, cancellation, and retry.
- This is a human-reviewed design task; lifecycle semantics are already established and must be preserved.
Current Behavior
The research composer and SidecarCard-based lifecycle cards expose the necessary data and actions but have weak hierarchy, inconsistent action placement, and little visual continuity between queued, searching, analyzing, writing, publishing, failed, cancelled, and ready states.
Desired Behavior
Create a cohesive research composer and lifecycle-card family with clear progress, source/report metadata, calm loading states, legible recovery actions, and strong continuity from request to child document.
Acceptance Criteria
- The audit covers composer empty/drafted/submitting/blocked/error states and every durable request stage: queued, searching, analyzing, writing, publishing, failed, cancelled, and ready.
- State changes retain a stable card identity and do not visually imply a new request on retry.
- Cancel, retry, remove, and open-child actions have consistent placement and hierarchy appropriate to each stage.
- Ready state clearly presents title, summary, source count, Planner provenance, and navigation to the ordinary child document.
- Loading/progress treatment respects reduced motion and does not rely on animation alone.
- Existing persistence-before-publication, observational-read, retry, cancellation, and child-publication behavior remains unchanged.
- Maggie approves the audit specimens before production migration.
Verification Commands
bun run typesbun run cibun test packages/editorbun run e2e
Primary Surfaces
/design-audit#authored-content- Research composer and lifecycle cards in
packages/editor - Parent document research request and child-document navigation
Expected PR Checks
- Repo required checks
Report Requirements
- Complete lifecycle state matrix
- Before/after screenshots at normal and narrow widths
- Reduced-motion and keyboard evidence
- Confirmation that request identity and publication semantics are unchanged
Implementation Notes
- A pending request remains an inline card with no URL, sidebar row, Conversation, or Decisions.
- Failure, cancellation, and retry preserve request identity; reads must not restart terminal work.
- Publication remains idempotent and persistent before the ready card or navigation row appears.
Stop Conditions
- The design implies a new product workflow such as standalone research workspaces or grandchildren.
- A visual change requires altering durable lifecycle or publication ordering.
- Lingua principale
- TypeScript
- Stelle
- 351
- Fork
- 20
- Merge medio
- 14h 7m
- PR unite (30g)
- 34
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di githubnext/chopin
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
githubnext/chopin#154 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
githubnext/chopin#149 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
githubnext/chopin#165 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 38/100
githubnext/chopin#163 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
githubnext/chopin#162 ·
Tutte le issue di githubnext/chopin
Issue simili
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Crush Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
ElementsProject/cln-application#167 · 1 commento · 1 reazione ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Quantco/pnpm-licenses#17 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100