Background
Based on the Prototyped code-ready design spec form Q1, we will work on an initial proof of concept to demonstrate a new, more scalable way to seed content

Approach

• Make it possible for editors of Dagbani Wikipedia to make a simple conversion edit by calling Wikifunctions.
• Make the feature production-ready, to be turned on in the new year
• Demonstrate use of the feature on Test Wikipedia (or a similar production test wiki)
• Prepare instrumentation to enable us to see if success metrics are met (in particular, “At least one article is organically using our feature on Dagbani Wikipedia”)
• Use case is based on the design prototype completed in Q1. Continue working on usability improvements in Q2, for implementation in Q3

Acceptance Criteria/Success Metrics
**Acceptance Criteria:

The feature is ready to be switched on in the new year and is using async pipeline, and is performant.

**Success metrics [Measured during Q3]:

• At least one article on Dagbani Wikipedia is using our feature organically without being reverted.
• We do not create regression or active breakage on Mediawiki. We limit MediaWiki P0 incidents related to this integration to no more than one per quarter.
• There is positive sentiment on Dagbani Wikipedia about the deployment of the feature, based on wiki conversations and checking in with our contacts.
• Related to this we will measure:
• How many users clicked on the ‘insert function’ entry point.
• Of the people who clicked on it, how many completed the task.
• Of the people who clicked on it, how many dropped out at each step [These logical points will be decided after UI is finalized] towards completion.

Stretch Goal (optional)

• Identify and prototype the next 2-3 use cases for next quarter
• We are ready to begin engineering work on the second use case in Q3