Page MenuHomePhabricator

Create essential articles: add a way back from "Translate or write" to the article pick step
Closed, ResolvedPublic1 Estimated Story Points

Description

Background

The Create essential articles flow has two steps: Pick your article (EssentialArticleStepPick) and Translate or write (EssentialArticleStepCreate). Confirming a pick saves it to the task metadata and moves to step 2, which displays the pick (title + approach) in the .article-box card. The parent view (EssentialArticleTool) owns currentStep.

Problem

Once a pick is confirmed there is no way back. Step 2 has no back affordance, and reloading makes it worse: the saved metadata restores the user straight into step 2. A user who mis-picked, changed their mind about the approach, or discovered the suggested article isn't what they want is stuck with it — there is no user-facing reset.

This affordance is also needed by the companion "definition of done" work: when a picked article turns out to already exist and not be attributable to the user, the intended UX is to prompt a re-pick — which requires a way back to step 1.

Proposed approach

Add a "Change article" control inside the .article-box card, aligned to the card's end (right in LTR):

  • Icon + text label, not icon-only: the label names the effect ("Change article"), which is clearer than a generic "Go back", and the requirement is that users understand it at a glance and find it when they look for it. Icon via CdxIcon + @wikimedia/codex-icons (e.g. cdxIconArrowPrevious), per repo convention.
  • Placement rationale: the card is the visual representation of the pick — the control that changes the pick belongs on it. That is also where users look first when they want a different article. A free-standing back button near the step header was considered, but it has a weaker association with the pick and the flow has no existing wizard-back convention to be consistent with.

Behavior:

  • Click → track a back-to-pick CTA event (with the current title/approach payload, like the step's other CTAs) → return to the pick step.
  • The saved metadata is not cleared by going back; it is overwritten only when the user confirms a new pick (existing confirm behavior). Backing out and returning (or reloading) without a new confirm restores the previous pick as today.
  • Checklist state is untouched by navigation (its per-run reset is in scope of the companion repeatability task, not this one).

Acceptance criteria

  • Step 2 ("Translate or write") offers a clearly labeled control to go back to the article pick step, visible without scrolling on desktop and mobile widths
  • The control is an icon + text button inside the .article-box card, using CdxIcon with a @wikimedia/codex-icons icon
  • Clicking it returns to the pick step and logs a back-to-pick CTA event
  • Going back does not clear the saved pick; confirming a new article overwrites it as today
  • The control is keyboard-focusable with an accessible name

New user-facing text goes through i18n/en.json + qqq.json.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Feat: Add "Change article" back-navigation to essential-article step 2repos/lpl/starterkit-v1!146ngkountasfeat/T433042-change-article-backmain
Customize query in GitLab

Event Timeline

ngkountas set the point value for this task to 1.

toluayo merged https://gitlab.wikimedia.org/repos/lpl/starterkit-v1/-/merge_requests/146

Feat: Add "Change article" back-navigation to essential-article step 2

srishakatux subscribed.

Done, considering we now have a "<- change articl"e on Step 2 to go back to Step 1.