Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

[Design] Redesign research components

Đang mở
#164 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
35/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
bun, typescript
Lĩnh vực
design, frontend

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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-content currently 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 types
  • bun run ci
  • bun test packages/editor
  • bun 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.
Ngôn ngữ chính
TypeScript
Star
351
Fork
20
Merge trung bình
14 giờ 38 phút
Pull request đã merge (30 ngày)
32

Hướng dẫn đóng góp

Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của githubnext/chopin

Tất cả issue của githubnext/chopin

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.