User story:

As a user of Collaborative Contributions on non-Wikipedia projects, I want to be able to associate an edit with an event.

Background:

The CampaignEvents extension is currently on all Wikipedias, Wikidata, one Wiktionary wiki (Malay Wiktionary), and Meta-Wiki. It may also be on other projects on the future, such as Commons, Wikisource, Wikitravel, etc. Some of these other projects have different ways to publish edits, and we want to ensure that whatever solution we pick for associating edits with an event can work for these projects too.

For example, Wikidata does not have the editing experience as Wikipedia. There isn't a separate editor dialog. So, we should look into Wikidata, and we should also see if there are other cases we should be aware of. We can the use this information to help inform a decision on which approach we take to associate an edit with an event.

Acceptance Criteria:

• Ensure basic functionality of edit association for the following projects:
  • Top priorities for investigation (i.e., take more time to thoroughly investigate):
    • Wikimedia Commons
    • Wikidata
    • Wikisource
    • Wiktionary
  • Secondary priorities (less contribution events, but still could be good to look into):
    • Mediawiki
    • Wikibooks
    • Wikiquote
    • Wikiversity
    • Wikispecies
    • Wikifunctions
    • Wikivoyage
    • Wikinews

Visual examples:

Editing on Wikidata, in which the user clicks "Publish" in top right corner to make change (desktop view)

Findings

Most projects (Wikibooks, Wikisource, Wikiquote, Wikiversity, Wikispecies, Wikivoyage, Wiktionary, and Wikinews) make use of a Wikipedia-like editing flow, which includes a pre-publish dialog where an edit summary field, optional preview, and a final "Publish changes" button before edits go live are involved. These projects would work well with the solutions and approaches that we explored for tracking collaborative contributions.

In contrast, in projects like Wikidata and Wikimedia Commons, edits are sometimes made to individual fields (e.g field information or structured data in Commons). Here, changes are mostly made inline, saved immediately after clicking “publish” on each statement or value, and no edit summary is requested. In Wikidata, for example, edit summaries are auto-generated unless the edit is a revert. For the Upload Wizard, the editing/upload process is step-by-step (Upload → Describe → License → Publish). There's no edit summary.

Wikifunctions presents a hybrid editing model that blends structured inputs with a traditional publication step. When users create or edit a function in Wikifunctions, they are prompted with a “Publish your changes” dialog before the edit is finalized. This dialog includes a text field for an edit summary. And when inserting functions inside of a Wikipedia article, the edit is queued locally until the final “Publish” action is confirmed (where the pre-publish conventional dialog comes up).

Link to explorations in Figma, with screenshots and sticky notes.