User stories:

For events/collaborative activities:

As an event organizer, I want to add a worklist for my event, so that prospective and active participants now that we will focus on and so that all articles within the worklist can be included in collaborative contribution tracking for the event.

As an event participant, I want to know which articles will be included in the event, so that I can begin participating in the event without needing much instruction/blockers and so that my edits can be tracked with greater ease and less effort on my part.

As an event participant, I want to be able to add articles to the worklist of the event (if permitted by the organizer), so that I can also take part in the event development and edit tracking.

As an event participant, I want to be able to easily edit the articles within the scope of an event, without needing to see the post-publication dialog every time.

For personal challenges:

As an editor who is interested in setting up personal challenges for myself, I want to be able to create a worklist of "to-do" tasks, so that I can easily track my progress against my goal and share my successes with others.

Background:

Some WikiProjects, communities, or events have defined worklists for their collaborative activities. For example:

WikiProjects:

• WikiProject Articles for Improvement on English Wikipedia: They will have an article to improve for the week.
• WikiProject Women in Red on English Wikipedia: Has a long list of redlinks (generated from Wikidata items) on articles to create that have not been created yet.

Events:

• Wikimedia Korea-Malaysia Friendship 2025 Editathon: This is an editathon event between South Korean and Malaysian Wikimedians. You will see that they have a worklist for articles in Malay, English, and Korean Wikipedias.
• WikiForHumanRights 2025 in Ghana/University Of Ghana: This event has an article list for articles in: English Wikipedia, Wikidata, Twi Wikipedia, Dagbani Wikipedia, Pidgin Wikipedia, Hausa Wikipedia.
• SheSaid 2025 in Nigeria: This list provides a list to a Wikidata query to find articles to improve on Wikidata, English Wikipedia, and Wikiquote.
• International Literacy Day 2025 in Gombe Network: This event provided a template for what participants need to add in order to include their edits in the final worklist.

If we allow organizers (and sometimes other editors/participants) to add a worklist to an event, then perhaps we can allow automatic tracking of participant edits to those articles. This could be another way to track edits, on top of the dialog after an edit is published and the dropdown within the edit summary. The idea is that, with more tracking options available, we're more likely to have more accurate data, since it can capture the different ways that people edit collaboratively.

In this sense, the work is a bit related to T400196. We are allowing ways for organizers and participants to further customize how the data is tracked.

Meanwhile, on the personal challenge front, we can imagine people creating many different personal challenges in the future. Some may be about creating/improving a certain number of articles or adding number of byes. Perhaps another approach is creating articles based on redlinks from a worklist.

How worklist configuration could work:

For events:

• Organizer has the option to add a worklist to an event
• Organizer has the option to decide who can add articles/wikidata items to worklist, with options including:
  • Only organizers of the event
  • Only organizers and participants of the event
  • All editors
• Worklist can accept following formats:
  • Wikidata item
  • Link to article/page
• Worklist probably needs a maximum number of links/characters

For individuals creating personal challenges:

• Editor can use Event Registration to input worklist (like an organizer)
• They would need not the event organizer right
• They would not need all organizer features

What data could be included in a worklist:

• Article to work on
• Guidance on what to change/tasks that editors can do (like add more references)
• Effort estimate from organizer
• Priority estimate from organizer
• Potential references/links/resources that can be used

How all editors can add items to a worklist for an organized event:

Maybe we can allow organizers to input a link to an editable wiki page with a worklist, if they want to allow anyone to edit the worklist. See details on how LPL handles worklists for its Community Lists feature below.

Or we can pull up a simplified version of Special:EditEventRegistration that only shows the worklist section (and editors can only add entries, but not remove them).

If they want to create a closed worklist, maybe they just input the worklist data as part of the event registration configuration process.

How worklist tracking could work:

• If someone logged in and registered for the event OR who created the personal challenge, and they are on a wiki of the event/personal challenge, and if they are editing an article on the worklist, that edit would be associated with event/challenge by default in the edit summary (with the dropdown). No effort would be needed on the editor's part to make the association - only if they want to remove the association.

Related work:

• T405754: Outreachy 31: Micro-task Generator for Organizers on Wikipedia
• Past early ideas for the collaborative contribution project (see concepts 2-4 for worklists could be developed + how they could interact with goals)

Integration with other tools & workflows:

• Suggested Edits: Perhaps worklists could be included in Suggested Edits. Idea shared by Growth:
  • Communities can create lists (potentially using the new Reader Lists functionality, if a public version for list building becomes available).
  • Administrators can then use Community Configuration to set up a new Suggested Edit tied to a list that reflects current community needs or aligns with active campaigns.
  • That list would then surface in the Suggested Edits feed through the custom filter created in Community Configuration
• Goal-setting (see design investigation): Maybe we could allow a goal to be on whether all articles in a given worklist were edited/created in the future. This is what ties this work to the personal challenge idea.
• Existing list-building tools: There are already a ton of tools, mostly off the wikis, that help people create worklists, such as the List-Building Tool and PetScan. You can see the full list of these tools on Topical List-Building Tools. Ideally, it would be nice if people could easily copy/paste the lists generated from these tools onto a wiki page or into Event Registration configuration, and then those lists could be used without additional formatting needed.
• Community Defined Lists, created by Language & Product Localization: Users can create worklists based on wikidata items, and then they add they HTML markers (<page-collection> and </page-collection>) to indicate that it is a worklist. Everything that is a valid wikilink to a mainspace article will be picked up as an article that is part of the page collection. That can be en:Cat, fr:Chat, or d:Q405, all valid. Lists of wikidata items is by far the most common usage. See Category:Pages including a page collection for all pages on Meta-Wiki with collections. Here is an example of worklist wikitext for the feature. Note that the formatting (different sections and numbered list (#)) make a nicer output but are not needed for the feature to work.

Acceptance Criteria:

• Develop design concepts for how an organizer can create a closed worklist (i.e., only editable by other event organizers)
• Develop design concepts for how an organizer can create an open worklist (i.e., editable by any editor)
• Explore how lists are made by some common list-building tools and determine if there are some common formats/structures that we should borrow from in order to have a more intuitive process for editors who want to create a worklist
• Note that we probably don't need to develop separate design concepts for associating the edit with the event, since any items from the worklist can be automatically assumed to be for the event, if a registered participant is working on the article during the event period.