Page MenuHomePhabricator

Article Creation Guidance Desktop Improvements
Closed, ResolvedPublic4 Estimated Story Points

Description

Summary

Article creation guidance flow was originally designed for mobile but later we made some changes to make it responsive for desktop too. This task aims to document some more changes we can make for Desktop.

Changes

01. Page heading + title input on step 1

Before
Screenshot 2026-05-11 at 10.02.58 PM.png (2,994×1,964 px, 234 KB)
  • "New article" is centered.
  • Title input ends midway across the column
After
Screenshot 2026-05-11 at 10.04.13 PM.png (2,994×1,964 px, 233 KB)
  • Standard MW special-page heading.
  • Title input spans the full content column, its bottom border aligns with the heading's underline.
  • Left-aligned, serif, single thin rule beneath. Body content flows below. ---

02. Remove the back arrow on this screen

Before
Screenshot 2026-05-11 at 10.15.58 PM.png (2,994×1,964 px, 337 KB)
  • A small ← icon hovers above the heading. Once the heading is left-aligned (point 1) it sits in dead space.
  • Lets style it similar to Recent Changes, Watchlist, Preferences.
After
Screenshot 2026-05-13 at 4.43.08 PM.png (3,018×1,894 px, 361 KB)
  • Remove the floating back-arrow entirely.
  • Use an explicit Back button in the step action area where back navigation is needed.

03. Manual Outline list - 3 column grid

Before
Screenshot 2026-05-11 at 10.20.53 PM.png (2,994×1,964 px, 380 KB)
  • Short-format cards (icon + name + one-line description) given a wide-format single-column stack.
  • Descriptions vary from one line to five. In a grid, rows inherit the tallest card; rhythm goes uneven.
  • "Suggest a new type" is placed centrally.
After
Screenshot 2026-05-11 at 10.21.26 PM.png (2,994×1,964 px, 534 KB)
  • 3-column CSS grid on desktop. Same card, smaller cell, easier to scan.
  • Consistent min-height per card + two-line ellipsis clamp on description.
  • Anchor to bottom-left with a thin top divider, reads as the list's footer action. ---

04. Title-already-exists step

Before
Screenshot 2026-05-11 at 10.25.07 PM.png (2,994×1,964 px, 297 KB)
  • Six stacked rows: warning, suggestion, "Selected subject" heading, card, button, link.
  • Wide Continue button and "View existing article" below it
After
Screenshot 2026-05-13 at 5.27.22 PM.png (3,018×1,894 px, 287 KB)
  • Warning and “View existing article” sit on the same line on desktop.
  • Suggested title appears on the next line so it reads as a secondary resolution option.
  • “Selected subject” is a quiet small label, not a bold heading. The card explains itself.
  • Narrow the subject card so it does not compete with the message above.
  • Right-align the action row to the title input’s right edge.
  • Keep the action row focused on step navigation: Back and Continue only.

05. Sources step: two columns + content block tips

Before
Screenshot 2026-05-11 at 10.15.58 PM.png (2,994×1,964 px, 337 KB)
  • Vertical stack on desktop.
  • Tips inside a collapsed accordion (mobile pattern).
  • Inline "+" Add button.
  • Oversized full-width Continue.
  • Loose heading/subtitle spacing.
After
Screenshot 2026-05-13 at 5.11.14 PM.png (3,018×1,894 px, 361 KB)
  • Two columns on desktop: URL input and actions on the left, source tips on the right.
  • Tips are shown as a static content block, not a collapsed accordion.
  • Tips block is top-aligned with the “Add sources” heading.
  • Tips hierarchy is clearer: “Tips for [type] articles” is a small quiet label, while “These source types work well:” is the bold heading.
  • Action row sits under the input with insight text on the left and Back / Continue actions on the right.
  • “Add source” is a Codex button next to the URL field. After a valid source is added, it appears below as a dismissible source item, and the same URL field clears and stays ready for another source.

06. Instructions step

Before
Screenshot 2026-05-11 at 10.33.58 PM.png (2,994×1,964 px, 320 KB)
  • "Start writing" centered.
  • Guidance card spans full content width with weak containment.
After
Screenshot 2026-05-13 at 5.19.14 PM.png (3,018×1,894 px, 368 KB)
  • Keep the guidance content in a capped reading column so the card and action feel connected.
  • Treat the guidance block as a contained card with clearer visual boundaries.
  • Right-align “Start writing” to the card’s right edge, not the full page edge.

07. Notability step

Before
Screenshot 2026-05-12 at 11.19.39 AM.png (3,842×2,078 px, 340 KB)
  • Each row reads as a stretched banner rather than a discrete pickable action.
After
Screenshot 2026-05-13 at 5.21.16 PM.png (3,018×1,894 px, 298 KB)
  • Present each notability option as a distinct selectable card.
  • Cap the option list width so the choices do not stretch into full-width banners.
  • Keep the cards in a vertical stack with consistent spacing for easier scanning.
  • Keep Back as an explicit secondary action below the option list.

Event Timeline

Pginer-WMF triaged this task as Medium priority.Apr 29 2026, 8:31 AM
Pginer-WMF raised the priority of this task from Medium to High.Apr 29 2026, 9:20 AM
SGautam_WMF raised the priority of this task from High to Needs Triage.Apr 29 2026, 11:06 AM
SGautam_WMF updated the task description. (Show Details)
Pginer-WMF lowered the priority of this task from High to Medium.Apr 29 2026, 1:46 PM

@SGautam_WMF, looking. at the initial step of the workflow on desktop the way "New article" title is displayed may be causing some issues:

  • The "New article" title position (centered) is unusual compared to other wiki tools (such as Recent Changes, Watchlist...).
  • Visual hierarchy between "New article" title and the "Article title" input makes the later look less as intended. The idea for the "article title" was to look as the title for the new page the user is providing.

b24e11a4f1.catalyst.wmcloud.org_wiki_Special_NewArticle(Wiki Tablet) (1).png (1,024×768 px, 44 KB)

Thanks @Pginer-WMF, I am planning to update the task with some more design details, and i will include your feedback too in there.

@Pginer-WMF i have documented proposed improvement, let me know if it aligns with your understanding.

@Pginer-WMF i have documented proposed improvement, let me know if it aligns with your understanding.

Thanks @SGautam_WMF. The layout improvements make sense. For a sequential process like this, having an explicit way to move back may still be convenient on desktop despite the easier access. to the browser buttons. It may be worth exploring if there are options to integrate it in a way that makes sense for desktop.

eamedina changed the task status from Open to In Progress.Jun 3 2026, 1:32 AM
eamedina claimed this task.
eamedina moved this task from Prioritized to In-progress on the LPL Hypothesis board.

Change #1297259 had a related patch set uploaded (by Eamedina; author: Eamedina):

[mediawiki/extensions/ArticleGuidance@master] Add desktop improvements

https://gerrit.wikimedia.org/r/1297259

Change #1297259 merged by jenkins-bot:

[mediawiki/extensions/ArticleGuidance@master] Add desktop improvements

https://gerrit.wikimedia.org/r/1297259

Change #1302901 had a related patch set uploaded (by Sbisson; author: Sbisson):

[mediawiki/extensions/ArticleGuidance@master] Fix 'line too long' lint warnings

https://gerrit.wikimedia.org/r/1302901

Change #1302901 merged by jenkins-bot:

[mediawiki/extensions/ArticleGuidance@master] Fix 'line too long' lint warnings

https://gerrit.wikimedia.org/r/1302901