User stories:

As an event organizer, I want to be able to co-create an article worklist with event organizers and participants, so that event participants can have a clear sense of what to work on and prospective participants can be potentially become interested in joining due to the articles covered.

As an event participant, I want to be able to see what articles I should work on, so that I can easily begin taking on tasks for an event.

As an event participant, I want to be able to add articles to the worklist, so that I can feel like a valued member of the event and so that I can also have an improved experience as related to collaborative contributions.

As an editor who cares about an article, I would like to learn about potential events related to improving the article, so that I can make a larger impact while working with others and connect with like-minded editors.

Background:

We want to allow the ability to create structured worklists for events for two main purposes:

• Improved tracking support for collaborative contributions
• New ways to surface and promote events to editors who may be interested in joining

Regarding collaborative contributions: We currently show a post-publication dialog upon every edit made by participants on the target wiki and during the event period. This is a tedious process for some event participants, particularly if they are more experienced and prolific editors and/or if they make multiple edits to the same article. To improve this situation, we want to allow the development of a worklist, so that if an article is being edited by an event participant and if the article is in the worklist during the event period, then we do not need to display the post-publication dialog. Rather, we will automatically associate the edit with the event.

Regarding event discovery: In Q4 of the 2025/26 fiscal year, we're focused on developing new ways of surfacing events to editors. We want to surface events that may potentially interest editors, and we hypothesize that one way to do this is connecting editors based on their edit history and the articles that will be worked on during the event. In particular, we're interested in experimenting with the immediate post-publish moment, in which an editor has saved a change. We haven't really done much experimentation in this space in the past, and perhaps some editors would like suggestions or next steps that they could take after saving an edit.

For this particular project concept, we want to identify editors who make significant contributions to an article, if the article will be worked on during an upcoming or ongoing event. In such a case, we want to make them aware of the event, so they have the option to learn more or even register by visiting the event page. Meanwhile, we know that not everybody will be interested in learning about new events, so we want easy ways to opt out of receiving such notifications as well.

Inspiration:

• https://microtask-generator.toolforge.org/ & https://fast-api.toolforge.org/ (older stable version) - user can generate a worklist based on categories, and then they receive article title, quality (such as start, stub, etc), quality rating (between 0 and 1), potential needs, topics, countries, etc) - perhaps we could also allow organizers and/or participants to manually add articles OR search categories to add articles to worklist, and then provide title & quality info & potential needs as well - could also help with goal-setting since needs are more clearly established.

Acceptance Criteria:

• If an organizer has created an event that is a contribution event,
  • A new tab should be automatically generated in EventDetails for the worklist, and it should appear before the Contributions tab
• On the new worklist tab,
  • If someone is an event organizer or registered event participant,
    • They can add articles to the worklist
      • Data to include: article title, article wiki
    • They can remove articles from the worklist
      • Organizers can remove all articles
      • Participants can only remove articles that they added
• If a registered participant is making an edit that can be associated with the event, and the article is already in the worklist,
  • They should not see the post-publication dialog
  • They should see confirmation message that edit was added to the event
• If an editor makes an edit that is on the worklist of an event, and if they have not seen the post-publication dialog to invite them to the event, and if they are not yet registered for the event,
  • They should see a post-publication dialog that encourages them to join the event or check out the event page to learn more
  • And they should have options to visit event page, decline visiting event page, and decline all further post-publication dialogs based on event discovery through article matches
• There should be a new option in Preferences to opt out of all post-publication dialogs based on event discovery through article matches
• A user should only have a specific event promoted to them once, but they can see multiple event promotions for different events

Out of scope, but may be included in post-MVP iterations:

• Only showing the post-publication dialog to those who have made a significant edit to the page, which can be one large edit or overall substantial total contributions. This can be measured by number of bytes or other criteria.
• A new sub-tab under Contributions that focuses on articles, which displays cumulative impact on articles over the course of the event (such as number of edits made, bytes added, references added, etc)
• The ability for organizers and/or participants to manually input data about the articles, including: article guidance, article priority
• The ability for participants to claim or be assigned articles
  • Multiple participants can perhaps work on the same article at the same time -- but, if they do, they should specify which part of the article or which tasks they will focus on so there is not duplicated effort
• Automatically generated information on the articles, which can help participants choose which article to work on and how to improve it, such as: suggested tasks, article quality score, and article topics
• The ability for the organizer to import a list of articles into the worklist