Page MenuHomePhabricator

Article Guidance: Article Type Selection (Manual Fallback)
Closed, ResolvedPublic4 Estimated Story Points

Description

Goal

  • Let users manually choose an article type when auto-detection from topic matching (T414902) is unavailable.
  • Keep users moving forward.

Scope

This is a section that appears below the persistent title input (from T414902), not a separate screen. The title remains visible and editable above.

When to show

This step appears when the user couldn't confirm a topic match from the title entry step (T414902). Two cases:

FromWhen
T414902 — "None of these? Pick a type instead"User rejected all disambiguation topics
T414902 — No Wikidata resultsZero search results

If topic matching (T414902) successfully identifies the article type, this step is skipped entirely.

Exit conditions

OutcomeWhat happens next
User clicks a type cardProceeds to notability check (T415485)
User's type is not listedSee "Exit path" below

Exit path

If none of the available type cards match, the user needs a graceful way forward. Options under exploration:

  • Continue without guided help: user proceeds directly to the editor without article-type-specific guidance.
  • Request a type: user is directed to a talk page to suggest a new type.

we will explore exit path design separately.

Type Cards

variant-a-type-cards-only.png (375×812 px, 45 KB)

  • Header: CdxButton (quiet) with CdxIcon (cdxIconArrowPrevious) for back navigation. Centered bold title: "New article".
  • Question heading: What is this?
  • CdxCard components stacked vertically, one for each article type outline the community has configured. A wiki might have 5 types or 20 depending on what their community defines. Each card has an icon, bold label, and short description.

Details

Event Timeline

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

I'd like to discuss the "Similar to existing articles" feature (in this ticket, states B through E). If there is a total of, say, 10 or 15 types to select from (will depend on community), the user will presumably browser through this list and upon not finding a match the user can provide a similar article that the feature will try to match back to the same 10-15 types from above. Am I understanding this redundancy correctly? I take it the assumptions are a) that the user has an idea of what the article type they want to create should be, and b) the user may have a knowledge of a similar article beforehand. Even with these assumptions it seems the goal is still to help the user narrow down and find the right type from the already visible list. I'd love to hear more about the reasoning behind this feature.

The user may very well conclude that the type/outline simply does not exist in the wiki, in which case it would be a valid exit way in my opinion. I think state E tries to get at this, though the messaging points them back to the same list above.

I'd like to discuss the "Similar to existing articles" feature (in this ticket, states B through E). If there is a total of, say, 10 or 15 types to select from (will depend on community), the user will presumably browser through this list and upon not finding a match the user can provide a similar article that the feature will try to match back to the same 10-15 types from above. Am I understanding this redundancy correctly? I take it the assumptions are a) that the user has an idea of what the article type they want to create should be, and b) the user may have a knowledge of a similar article beforehand. Even with these assumptions it seems the goal is still to help the user narrow down and find the right type from the already visible list. I'd love to hear more about the reasoning behind this feature.

The user may very well conclude that the type/outline simply does not exist in the wiki, in which case it would be a valid exit way in my opinion. I think state E tries to get at this, though the messaging points them back to the same list above.

Thanks for these points @eamedina , i have simplified the scope of this task and we will take care of exit path solutions in this task - T418408

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

[mediawiki/extensions/ArticleGuidance@master] Manual article type selection refinement

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

Change #1245524 merged by jenkins-bot:

[mediawiki/extensions/ArticleGuidance@master] Refine manual article type selection

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

Pginer-WMF moved this task from Design Signoff to Product Signoff on the LPL Hypothesis board.

Key functionality works as expected. Minor adjustment proposed as separate follow-up ticket: T421225: Order types of articles alphabetically