Page MenuHomePhabricator

Improved URL for triggering Growth Suggested Edits
Open, Stalled, Needs TriagePublicFeature

Description

Feature summary (what you would like to be able to do and where): Currently URLs to trigger a suggested edit on a page, makes it challenging for tool builders and editors to create to-do lists related to Suggested edits. I would like a simple url append similar to the "&veaction=edit" for triggering VE on a page.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

  • I want to build a tool that triggers suggested edit workflows for a WikiProject. In order to generate a list, I search the search index if there are actions for articles in the WikiProject list, and then want to create a one click list of urls for generating veedits on a page. I would like to be able to do this with as light of weight of a template as possible.
  • I want to generate a to do list for an editathon. I search for suggested edits, using an intersection of Categories and the Search on Petscan. Petscan allows me to easily output a list of URLS and pagenames for the list of articles. I would like a simple url variable (i.e. &suggestededitx=true) to append to the url, so that I can create a bunch of "ready" links for my participants.

Benefits (why should this be implemented?): This would make the Suggested Edits tools more readily available for Javascript, Bot and query related workflows.

Event Timeline

I love this, and my request is very similar to this one :)

Feature summary: Provide a way to programmatically determine if a specific Growth team structured task (e.g., add-a-link, add-an-image) is available for a given article, and enable a URL parameter to deep-link directly into that identified task workflow.

Use case(s):
We¹ are building a tool that uses Liftwing's API to check whether a particular structured task—such as adding links—is applicable for a given article. If the model indicates a task is available, I want to generate a direct URL that opens the Growth interface for that exact task on that article. Currently, even if I can detect task availability programmatically, there’s no straightforward way to construct a link that launches the structured task UI pre-filled for the article and task type.
This forces tool builders to either send users to the generic suggested edits feed—where the task may not appear—or to build custom UI mimicking Growth’s workflow, which duplicates effort and can drift from the official experience.
¹ T405754: Outreachy 31: Micro-task Generator for Organizers on Wikipedia (application)

Benefits:

  1. Enables seamless integration between ML-based task detection tools and Growth’s structured task interface.
  2. Reduces labor for editors and campaign organizers who want to work from curated, model-informed task lists.
  3. Keeps task execution within the maintained, user-tested Growth environment rather than encouraging divergent implementations.
  4. Supports scalable task routing for bots, dashboards, and external curation platforms without requiring full UI re-engineering.

@SEgt-WMF I had a chance to discuss some with Growth engineers. FYI, the availability of Growth tasks is not determined by any Liftwing API. It is determined by weighted tags in CirrusSearch.

In general we like this idea, and technically it's feasible. But it doesn't sound simple, and doesn't relate to our current focus around Account Creation experiments.

This actually relates a little more to what @ppelberg and the Editing team are thinking about: Suggestion Mode and exposing edit suggestions in more places. That being said, I don't imagine this request quite fits within their immediate plans.

One other consideration is that tooling like this might cause complications for A/B testing Suggested Edits. But I don't think that's a blocker, just something we would need to think about solving.

My suggestion: let's set aside some time to connect at the WE1 offsite and plan ahead for a future where edit suggestions (like Growth's Suggested Edits, and Editing's Suggestion Mode) are easier to integrate for organizers and maintainers of WikiProjects. (FYI @ifried )

KStoller-WMF changed the task status from Open to Stalled.Jan 30 2026, 3:38 PM

Marking as stalled for now, but I would love to revisit this idea in the future because I do think an idea like this fits into the wider Contributor Strategy.

Hey @KStoller-WMF thank you so much for looking into this with Growth engineers and also sharing these thoughtful insights!
I loved your suggestion about connecting at the WE1 offsite to plan ahead. I'm wondering if a potential approach could be similar to what you did with the Revise tone experiment. As far as I understood the flow was something like:

a) find pages that apply,
b) trigger VisualEditor on that page with a specific variant of the “tone” check shown,
c) return contributors to the Growth workflow once they’re done.

I’m wondering if that flow could serve as a reusable template for other "micro taks" in the future?

Also, if possible (and useful!), I’d be interested to understand more about how tooling like this might complicate A/B testing for Suggested Edits, just in case I can help brainstorming mitigations or other possibilities early on.

And I agree! I do think this fits into the Contributors Strategy perspective. Particularly by simplifying the experience of how volunteers receive recommendations (point 1) as this would provide:

  1. "Modular and customizable experiences to suit diverse community needs" (i.e. Organizers online and offline)
  2. And would "[e]nable communities to direct volunteers to where they’re needed most" (i.e. concrete mini tasks to improve the quality of Vital Knowledge)

Looking forward to connecting more at the WE1 offsite.