Page MenuHomePhabricator

Make unsupported topics visible (with low prominence) in article guidance
Closed, ResolvedPublic4 Estimated Story Points

Description

As part of Article Guidance (T396029), by typing the title for a new article, users can select the specific subject for the article. The list is based on Wikidata items. Currently, it only shows those items that are supported by the current set of outlines defined. However, when the Wikidata item is not supported by an outline, the item is completely hidden from the list, which can cause confusion (is the topic not on wikidata? maybe under a different name?).

b24e11a4f1.catalyst.wmcloud.org_w_index.php_title=Special_NewArticle&newarticletitle=Paris(Wiki Mobile) (1).png (320×568 px, 33 KB)

This ticket proposes to adjust the treatment of matching items that are not supported by an existign outline:

  • For cases where an article already exists, we can just display them in the results. When users select, they will reach the existing view inviting them to edit those further (T420334).
  • For cases where an article does not exist for the Wikidata item, we can display it in a way that communicates that it is not supported yet by an outline (de-emphasized, with a label...) and de-prioritize it in the list of the results (shown at the end or in a separate group at the bottom). Selecting these could lead to a similar view as (T420334) where we confirm that it is not supported yet and provide alternatives: create with the regular non-guided experience (directing users to Visual Editor or Article Wizard) and request support for the type of the selected article (talk page message with info on the selected article not supported yet).

In this way, users will know that their query was understood by the system and that the element they want to create an article for is not supported yet.
This opens an opportunity to instrument and identify these cases too. In the context of the experiment, we may want to exclude and/or analyze separately these users that Article Guidance could not support yet.

UX Design Updates

Search results

en.t421274-master.mediawiki.mwdd.localhost_8080_w_index.php_title=Special_NewArticle&mobileaction=toggle_view_mobile(Moto G4) (2).png (1,080×1,920 px, 367 KB)
  • Supported items appear first (up to 5), unsupported items appear after (up to 3)
  • Supported items show their outline label (e.g. "actor"); unsupported items show no label
  • Unsupported items are selectable and lead to the unsupported topic step
  • When all results are unsupported, all are shown (up to 3)
  • When all results are supported, behaves as before (up to 5)

Unsupported topic step

en.t421274-master.mediawiki.mwdd.localhost_8080_w_index.php_title=Special_NewArticle&mobileaction=toggle_view_mobile(Moto G4) (4).png (1,080×1,920 px, 194 KB)

Structure:

  • Topic card: CdxCard showing selected Wikidata item (thumbnail, title, description), non-interactive
  • Section heading: <h3> — "No guidance for this topic yet"
    • @font-size-medium, @font-weight-bold, margin: 0 0 12px 0
  • Option list: icon + title + description rows with @border-color-subtle dividers (same pattern as NotabilityStep)

Option 1 — Request support for this type

  • Icon: cdxIconUserTalk in @color-progressive
  • Title: "Request support for this type" — @font-weight-normal, @color-progressive
  • Description: "Ask the community to add guidance for this type of article." — @font-size-small, @color-subtle
  • Action: opens project talk page and prefill the talk-page request with the selected article details, including title, Wikidata QID/link, description, source wiki, and intended article, so community members have enough context to create a matching outline later.

Option 2 — Start writing

  • Icon: cdxIconArticle in @color-progressive
  • Title: "Start writing" — @font-weight-normal, @color-progressive
  • Description: "Write this article without article guidance." — @font-size-small, @color-subtle
  • Action: opens VisualEditor for the article title

Event Timeline

Pginer-WMF triaged this task as High priority.
Pginer-WMF added a project: Design.
Pginer-WMF renamed this task from Keep unsupported topics visible (in a less prominent way) in article guidance to Make unsupported topics visible (with low prominence) in article guidance.Mar 25 2026, 10:04 PM
Pginer-WMF updated the task description. (Show Details)
SBisson changed the task status from Open to In Progress.Apr 14 2026, 2:17 PM
SBisson claimed this task.
SBisson moved this task from Prioritized to In-progress on the LPL Hypothesis board.

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

[mediawiki/extensions/ArticleGuidance@master] Show unmatched search results

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

For the "Unsupported topic step" the alternatives listed make sense, but I wonder if we may want to add anothe rone like this:

Select from the supported types
Find in the list of supported types one that applies to the subject.

This would be equivalent to the "Pick a type instead" action shown at the bottom of the search results.

I'm proposing this since the exact type may not be supported but other types may apply. An example I found recently (T421255#11832781) was of a company that was an instance of the Wikidata item Company (Q783794), but the "Company" outline is actually based on the "Business" Wikidata item (Q4830453) instead. Would in this scenario make sense to let the user use the Business-based outline? @SGautam_WMF What do you think?

(If this makes sense, or needs further discussion, we can create a separate ticket if needed)

Change #1270984 merged by jenkins-bot:

[mediawiki/extensions/ArticleGuidance@master] Show unmatched search results

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

@Pginer-WMF the case you are describing above where the user selects a unmatched wikidata search result, then manually select an outline, is different enough and goes against some of the assumptions we have in the code to warrant it's own task, design, and discussion.

@Pginer-WMF the case you are describing above where the user selects a unmatched wikidata search result, then manually select an outline, is different enough and goes against some of the assumptions we have in the code to warrant it's own task, design, and discussion.

Thanks for the input. Being a non-trivial change, it makes sense to check how the system works in practice after the update and decide then whether further adjustments are needed.

Supported items appear first (up to 5), unsupported items appear after (up to 3)

I think we may need to adjust the algorithm. Currently if the first 7 most relevant results are supported, we are discarding results 6 and 7 to include some unsupported ones that are less relevant. That does not make much sense.

I think it may be better to support it in this way:

Supported items appear first (no limit), unsupported items appear after (up to 3). Total number of items limited to maximum 8.

I think it may be better to support it in this way:

Supported items appear first (no limit), unsupported items appear after (up to 3). Total number of items limited to maximum 8.

Of course

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

[mediawiki/extensions/ArticleGuidance@master] Show up to 8 search results, including up to 3 unsupported

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

Change #1277639 merged by jenkins-bot:

[mediawiki/extensions/ArticleGuidance@master] Show up to 8 search results, including up to 3 unsupported

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

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

Items seem to be listed now as proposed. Small visual adjustments can take place in a follow-up ticket: T424803: Adjust the list of Wikidata items for unsupported items in Article Guidance