Complete task-oriented operator UX workflows

Abierto
  • ¿Algo no está bien?
#41 9 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
backend-api-design, documentation, full-stack, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
0
Forks
0
Merge medio
11 min
PR fusionados (30 d)
4

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DataTalksClub/relay

Todos los issues de DataTalksClub/relay

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.