Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Complete task-oriented operator UX workflows

オープン
  • 何か問題がありますか？
#41 コメント 9 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
backend-api-design, documentation, full-stack, testing

調査の方向性

Start with docs/audits/2026-10-02-ux-completion.md, which contains the implementation and historical local test/browser evidence. Review the UX01–UX18 responses and acceptance checklist, then inspect the independent commit-review receipts when they arrive and confirm the current full suite and checks pass. Done means reviewed changes are committed and pushed, with human validation and deployment explicitly remaining out of scope.

索引モデルが issue の本文から書いたものです。

説明

The operator interface makes campaign preparation, recipient management, delivery investigation, and setup difficult to navigate. Implement the task-oriented UX audit while preserving the current shared design-system styling.

Scope: audited operator workflows, audience/contact eligibility and scope, draft/review/test-send/cancel/schedule, unified email activity, block composer, sender setup, documentation navigation, operational jobs/schedules, accessibility and local performance checks. Required admin API/schema dependencies must have an explicit reviewed integration boundary; foreign work must be preserved.

Acceptance:

  • Audit UX01–UX18 have implemented responses and disclosed limitations.
  • Real scheduled dispatch, cancellation, outbox recovery, timezone/DST and stale-review guards pass tests.
  • Campaign test sending enqueues durable work instead of contacting a provider in an HTTP handler; queue acceptance is distinct from delivery.
  • Composer/import, confirmation, navigation/scope, eligibility, activity and operations regressions pass.
  • Independent tester runs current full suite and checks; independent product acceptance follows PASS.
  • Reviewed changes are committed and pushed to a feature branch, preserving local DB/scratch files and foreign work; no deployment.

Compatibility explicitly scoped: existing operator bookmarks in the audit/demo walkthrough use documentation workflow and endpoint-group anchors. Keep the old full reference and hash mapping for one operator migration window ending 4 November 2026. Tests cover the old anchors and destination access. Staff request logs for /api-docs/legacy/ provide observability; inspect usage before removing that route, template, and mapping in a separate cleanup issue. Do not extend this compatibility path to new API contracts.

Human validation remains separate: actual-user and human screen-reader sessions, real email-client rendering, authenticated deployed-environment verification and PostgreSQL query-plan validation. Code may be committed with Refs while these are unverified.

Implementation and historical local test/browser evidence: docs/audits/2026-10-02-ux-completion.md; independent commit-review receipts will follow. User explicitly requested commit and push on 4 October 2026.

主要言語
Python
スター
0
フォーク
0
平均マージ
8時間 34分
マージ済み PR（30日）
10

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DataTalksClub/relay のほかの issue

DataTalksClub/relay の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。