Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Design] Redesign research components

未关闭
#164 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
bun, typescript
领域
design, frontend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
TypeScript
星标
351
派生
20
平均合并
14 小时 38 分钟
30 天内合并 PR
32

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

githubnext/chopin 的其他 Issue

查看 githubnext/chopin 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。