Files
pipelines/docs/ui-ux-review.md
T

43 lines
2.5 KiB
Markdown

# UI/UX review: October 8, 2026
Five independent read-only reviewer sessions inspected executed `Model.View`
renders of Home, pipeline details, selected/focused/scrolled stages, native
delivery, and run inspection at 80/120/160 columns. Fixes were applied between
rounds. Snapshot review does not establish color accessibility or phone delivery.
| Round | Findings and changes |
| --- | --- |
| 1 | Added stage row ranges, horizontal graph overflow arrows/pan hint, and full-height column separators. |
| 2 | Balanced graph/detail space; expanded focused details; added textual focus/selection and complete selected-run headings; made title truncation explicit. |
| 3 | Exposed tools/notify in narrow configuration columns; preserved run statuses separately from shortened names; corrected run page size. |
| 4 | Made pinned field headings follow the actual scrolled group; exposed page-scroll keys; preserved HTTP/HTTPS in compact endpoint text. |
| 5 | No material remaining usability findings in the reviewed renders. |
Requested changes: `n`/`p` select next/previous stages on pipeline details,
wrap at either end, reset detail scroll, and reveal the selected graph stage.
Home `n` still creates a pipeline; text-entry/modal pages retain their own keys.
The global ntfy server URL/topic now appear in the top bar beside the server
address, instead of a home-page panel. Extremely narrow terminals truncate text
with an ellipsis rather than overflowing.
Verification executed after changes:
- `go test -race -count=1 ./...`
- `go vet ./...`
- Go server and TUI builds.
- Actual TUI through a pseudo-terminal: connected to the local server, opened
the published anime pipeline, verified top-bar ntfy URL/topic, `n`/`p`
next/previous/wrap, Tab focus, Esc home, and Home `n` opening the draft form.
`PIPELINES_UX_SNAPSHOT_DIR=<directory> go test ./internal/tui -run
TestUIUXReviewSnapshots -count=1` regenerates rendered snapshots without server
mutations. Temporary snapshot/reviewer artifacts are under the session's
approved temporary directory, not committed runtime data.
The real anime pipeline is `examples/anime-today.md`: dated web evidence →
verify/enrich → Markdown report → native ntfy attachment, using the system
connection. It is submitted as **anime episodes today v1**, pipeline **8**, with
no schedule. Its full model/web/phone execution has **not been tested**. The
LiveChart schedule was fetched during source investigation; the final delivery
stage uses the existing native publisher, not credentials handled by a model.