ux.sgit.ai

Findings / UX-020

The best reader feature is buried under metadata and a long italic abstract

OpenMediumFailurenewsroom.sgit.ai

What we saw

On the lead article (about 8,000 words) a phone reader scrolls past a three-line breadcrumb, a byline with two version numbers, 12 tag pills and a 250-word italic abstract before reaching the "Five readers" block.

Why it matters

The short version that would let a reader decide is found only by those who already decided to read.

The fix

Title and standfirst; a byline that says how it was made, date and reading time; the short version in three or four sentences; reader views as one row; then the article. Tags and versions to the foot.

The record

StatusOpen
SeverityMedium
KindFailure: works against the reader
Productnewsroom.sgit.ai, site
Wherehttps://newsroom.sgit.ai/articles/hope-or-enforcement.html
ProblemsBuried content
VisibilityObvious: every reader sees it, every time they reach that point
RecommendationShow it up front: put the signal the reader decides by (length, author, short version, real numbers) where they look first
AreaArticle page
BreaksSay how long, and what kind, before the reader commits
Observed2026-10-11, v0.6.4
Last checked2026-10-11, v0.7.1
SourceReview: article page and feedback
PrototypeArticle & reader primitives, route article/hope-or-enforcement, in three directions

Previous: UX-019 Search only matches titles, teasers and tags

Next: UX-021 Author tooling is shown to every reader