Growth/Personalized first day/Structured tasks/Add a link/es

Esta página describe el trabajo del equipo de Crecimiento en la tarea estructurada "añadir un enlace", que es un tipo de tarea estructurada que el equipo de Crecimiento ofrece a través de la página de inicio para recién llegados. Esta página contiene los principales recursos, diseños, preguntas abiertas y decisiones. La mayoría de las actualizaciones sobre el progreso se publicarán en la página general de Actualizaciones del equipo de crecimiento. Algunas actualizaciones grandes o detalladas serán publicadas aquí.

Desde agosto de 2021, la primera iteración de esta tarea se despliega en la mitad de las nuevas cuentas creadas en las Wikipedias árabe, checa, vietnamita, bengalí, polaca, francesa, rusa, rumana, húngara y persa. Hemos analizado los datos de las dos primeras semanas de despliegue de la función, y encontramos que los recién llegados están haciendo muchas de estas ediciones, y que tienen bajas tasas de reversión. Las conclusiones de este análisis nos han llevado a introducir mejoras en la función, y los resultados nos animan a ampliar el despliegue de esta funcionalidad a más wikis.

Puedes ver lo que estamos construyendo en estos prototipos interactivos. Ten en cuenta que, al tratarse de prototipos, no todos los botones funcionan:


 * Móvil
 * Escritorio

'''Los miembros del equipo presentaron los antecedentes, el algoritmo, la implementación y los resultados de este trabajo en Wikimania 2021. Puedes ver el vídeo aquí. and the '''

Situación actual

 * 2020-01-07: primera evaluación de la viabilidad del algoritmo de recomendación de enlaces
 * 2020-02-24: evaluación de la mejora del algoritmo de recomendación de enlaces
 * 2020-05-11: discusión de la comunidad sobre las tareas estructuradas y las recomendaciones de enlace
 * 2020-05-29: wireframes iniciales
 * 2020-08-27: inicio de la fase backend
 * 2020-09-07: primera ronda de pruebas de usuario del diseño para móviles
 * 2020-09-08: llamamiento a la comunidad para discutir sobre los últimos diseños
 * 2020-10-19: segunda ronda de las pruebas de usuario de los diseños para móviles
 * 2020-10-21: primera ronda de las pruebas de usuario de los diseños de escritorio
 * 2020-10-29: inicio de la fase frontend
 * 2020-11-02: segunda ronda de las pruebas de usuarios de los diseños de escritorio
 * 2020-11-10: Solicitud de opinión a las comunidades árabe, vietnamita y checa sobre los diseños
 * 2021-04-19: añadidas secciones en Terminology and Measurement
 * 2021-05-10: pruebas en producción en nuestras cuatro wikis piloto
 * 2021-05-27: desplegada en la mitad de los recién llegados de las Wikipedias en árabe, vietnamita, checo y bengalí
 * 2021-07-21: desplegado a la mitad de los recién llegados en las Wikipedias polaca, rusa, francesa, rumana, húngara y persa.
 * 2021-07-23: análisis publicados de las dos primeras semanas de despliegue de la función.
 * 2021-08-15: presentación en Wikimania sobre los antecedentes, la implementación, el algoritmo y los resultados.
 * Siguiente: mejoras menores, despliegues sucesivos en más wikis y análisis más profundos.

Resumen
Tareas estructuradas están pensadas para desglosar las tareas de edición en flujos de trabajo paso a paso que tengan sentido para los recién llegados y en los dispositivos móviles. El equipo de crecimiento considera que la introducción de estos nuevos tipos de flujos de trabajo de edición permitirá que más personas nuevas comiencen a colaborar en Wikipedia, algunas de las cuales aprenderán a realizar ediciones más importantes y se involucrarán con sus comunidades. Después de discutir la idea de las tareas estructuradas con las comunidades, decidimos construir la primera tarea estructurada: "añadir un enlace". Esta tarea utilizará un algoritmo para señalar palabras o frases que pueden ser buenos wikilinks, y los recién llegados pueden aceptar o rechazar dichas sugerencias. Con este proyecto queremos obtener aprendizajes sobre las siguientes cuestiones:


 * ¿Las tareas estructuradas son atractivas para los recién llegados?
 * ¿Los recién llegados consiguen realizar tareas estructuradas en el móvil?
 * ¿Generan ediciones valiosas?
 * ¿Conducen a algunos recién llegados a aumentar su participación?

¿Por qué wikienlaces?
Lo que sigue es un extracto de la página tareas estructuradas, que explica por qué elegimos desarrollar "añadir un enlace" como la primera tarea estructurada.

En la actualidad (mayo de 2020), el equipo de Crecimiento quiere priorizar el flujo de trabajo de "añadir un enlace" sobre el resto de los que aparecen en la tabla anterior. Aunque otros flujos de trabajo, como "copyedit", parecen ser más valiosos, hay una serie de razones por las que quisimos empezar primero con "añadir un enlace":


 * A corto plazo, lo más importante que queremos demostrar es que las "tareas estructuradas" pueden funcionar. Por lo tanto, tenemos que construir la más sencilla, para poder desplegarla a los usuarios y obtener aprendizajes, sin tener que invertir demasiado en la primera versión. Si la primera versión funciona bien, entonces tendremos la seguridad para invertir en otros tipos de tareas que son más difíciles de construir.
 * "Añadir un enlace" parece ser el más sencillo para nosotros porque ya existe un algoritmo construido por el equipo de WMF Research que parece hacer un buen trabajo sugiriendo wikienlaces (ver la sección Algoritmo).
 * Añadir un wikilink no suele requerir que el recién llegado escriba nada por su cuenta, algo que creemos que nos hará especialmente sencillo el diseño y desarrollo -y al nuevo usuario cumplir-.
 * Añadir un wikienlace parece ser una edición de bajo riesgo. En otras palabras, el contenido de un artículo no puede verse tan comprometido por añadir enlaces de forma incorrecta como por añadir referencias o imágenes de forma incorrecta.

Diseño
Esta sección contiene nuestro concepto de diseño actual. Para ver la totalidad de las reflexiones en torno a los diseños de la tarea estructurada "añadir un enlace", , que contiene antecedentes, historias de usuario y conceptos de diseño iniciales.

Nuestros diseños evolucionaron a través de varias rondas de pruebas de usuarios e iteraciones. A partir de diciembre de 2020, hemos establecido los diseños que realizaremos en la primera versión de esta función. Puedes verlos en estos prototipos interactivos. Ten en cuenta que se trata de prototipos, por lo que no todos los botones funcionan:


 * Mobile
 * Desktop

Revisión comparativa
Cuando diseñamos una función, buscamos funciones similares en otras plataformas de software fuera del mundo de Wikimedia. Estos son algunos de los aspectos más destacados de las revisiones comparativas realizadas para preparar la función de ediciones sugeridas de Android, que siguen siendo relevantes para nuestro proyecto.


 * Task types – are divided into five main types: Creating, Rating, Translating,  Verifying content created by others (human or machine), and Fixing content created by others.
 * Visual design & layout – incentivizing features (stats, leaderboards, etc) and onboarding is often very visually rich, compared to pared back, simple forms to complete short edits. Gratifying animations often compensate for lack of actual reward.
 * Incentives – Most products offered intangible incentives grouped into: Awards and ranking (badges) for achieving set milestones, Personal pride and gratification (stats), or Unlocking features (access rights)
 * Users motivations – those with more altruistic motivations (e.g., help others learn) are more likely to be incentivized by intangible incentives than those with self-interested motivations (e.g., career/financial benefits)
 * Personalization/Customization – was used in some way on most apps reviewed. The most common customization was via surveys during account creation or before a task; and geolocalization used for system-based personalization.
 * Guidance – Almost all products reviewed had at least basic guidance prior to task completion, most commonly introductory ‘tours’. In-context help was also provided in the form of instructional copy, tooltips, step-by-step flows,  as well as offering feedback mechanisms (ask questions, submit feedback)

Initial wireframes
After organizing our thoughts and doing background research, the first visuals in the design process are "wireframes". These are simply meant to experiment and display some of the ideas we think could work well in a structured task workflow. For full context around these wireframes, see the.

Mockups para móviles: agosto de 2020
Translate this section

Nuestro equipo discutió sobre los wireframes de la sección anterior. Hemos considerado lo que sería mejor para los recién llegados, teniendo en cuenta las preferencias expresadas por los miembros de la comunidad y pensando en las limitaciones técnicas. En agosto de 2020, pasamos a la creación de mockups, destinadas a mostrar con más detalle el aspecto que podría tener esta funcionalidad. Estos mockups (o versiones similares) se utilizarán en las discusiones del equipo, los debates de la comunidad y las pruebas de usuario. Una de las cosas más importantes que hemos tenido en cuenta con estos mockups es la preocupación que hemos escuchado constantemente por parte de los miembros de la comunidad durante la discusión: las tareas estructuradas pueden ser una buena manera de introducir a los recién llegados a la edición, pero también queremos asegurarnos de que puedan encontrar y utilizar las interfaces de edición tradicionales si están interesados.

Traducción realizada con la versión gratuita del traductor www.DeepL.com/Translator

Tenemos mockups para dos diseños de concepto diferentes. No pretendemos necesariamente elegir un concepto de diseño u otro. Más bien, los dos conceptos pretenden demostrar enfoques diferentes. Nuestros diseños finales pueden contener los mejores elementos de ambos conceptos:


 * Concepto A: la edición de la tarea estructurada tiene lugar en el Editor Visual. El usuario puede ver todo el artículo y pasar del "modo recomendado" al editor de código o editor visual. Menos centrado en la inclusión de los enlaces, pero con un acceso más fácil a los editores visuales y de código.
 * Concepto B: la edición de la tarea estructurada tiene lugar en una nueva sección propia. Al usuario se le muestra sólo el párrafo del artículo que necesita su atención, y puede pasar a editar el artículo si lo desea. Menos distracciones al añadir enlaces, pero un acceso más distante a los editores visuales y de código.

Por favor, ten en cuenta que este conjunto de maquetas se centra en el flujo y la experiencia del usuario, no en las palabras y el lenguaje. Nuestro equipo realizará un proceso para determinar la mejor manera de redactar las palabras de la función y explicar al usuario si debe añadirse un enlace.



Static mockups

Para ver estos conceptos de diseño, recomendamos ver todas las diapositivas a continuación.



Interactive prototypes

You can also try out the "interactive prototypes" that we're using for live user tests. These prototypes, for Concept A and for Concept B, show what it might feel like to use "add a link" on mobile. They work on desktop browsers and Android devices, but not iPhones. Note that not everything is clickable -- only the parts of the design that are important for the workflow.

Preguntas clave

Al examinar estos diseños, nuestro equipo confía en las respuestas a una serie de preguntas esenciales:


 * 1) ¿Debería la edición ocurrir en el artículo (más contexto)?  ¿O en una experiencia dedicada a este tipo de edición (más enfoque, pero mayor salto para ir a usar el editor)?
 * 2) ¿Qué pasa si alguien quiere editar el destino del enlace o el texto?  ¿Debemos impedirlo o dejar que vayan a un editor estándar?  ¿Es esta la ocasión de explicarles cómo funciona el editor visual?
 * 3) Sabemos que es fundamental que apoyemos a los recién llegados a descubrir las herramientas de edición tradicionales. ¿Pero cuándo lo hacemos? ¿Lo hacemos durante la experiencia de la tarea estructurada con recordatorios de que el usuario puede ir al editor? ¿O periódicamente en los hitos de finalización, por ejemplo, después de terminar un cierto número de tareas estructuradas?
 * 4) ¿Es "bot" el término correcto en este caso? ¿Qué otras opciones hay? ¿"Algoritmo", "Ordenador", "Computadora", "Automático", "Máquina", etc.?"   ¿Qué podría ayudar a transmitir mejor que las recomendaciones automáticas pueden fallar y que es importante la aportación humana?

Mobile user testing: September 2020
Background

During the week of September 7, 2020, we used usertesting.com to conduct 10 tests of the mobile interactive prototypes, 5 tests each of Concepts A and B, all in English. By comparing how users interact with the two different approaches at this early stage, we wanted to better understand whether one or the other is better at providing users with good understanding and ability to successfully complete structured tasks, and to set them up for other kinds of editing afterward. Specific questions we wanted to answer were:


 * Do users understand how they are improving an article by adding wikilinks?
 * Do users seem like they will want to cruise through a feed of link edits?
 * Do users understand that they're being given algorithmic suggestions?
 * Do users make better considerations on machine-suggested links when they have the full context of the article (like in Concept A)?
 * Do users complete tasks more confidently and quickly in a focused UI (like in Concept B)?
 * Do users feel like they can progress to other, non-structured tasks?

Key findings


 * The users generally were able to exhibit good judgment for adding links. They understood that AI is fallible and that they have to think critically about the suggestions.
 * While general understanding of what the task would be ("adding links") was low at first, they understood it well once they actually started doing the task. Understanding in Concept B was marginally lower.
 * Concept B was not better at providing focus. The isolation of excerpts in many cases was mistaken for the whole article. There were also many misunderstandings in Concept B about whether the user would be seeing more suggestions for the same term, for the same article, or for different articles.
 * Concept A better conveyed expectations on task length than Concept B. But the additional context of a whole article did not appear to be the primary factor of why.
 * As participants proceed through several tasks, they become more focused on the specific link text and destination, and less on the article context. This seemed like it could lead to users making weak decisions, and this is a design challenge. This was true for both Concepts A and B.
 * Almost every user intuitively knew they could exit from the suggestions and edit the article themselves by tapping the edit pencil.
 * All users liked the option to view their edits once they finished, either to verify or admire them.
 * “AI” was well understood as a concept and term. People knew the link suggestions came from AI, and generally preferred that term over other suggestions. This does not mean that the term will translate well to other languages.
 * Copy and onboarding needs to be succinct and accessible in multiple points. Reading our instructions is important, but users tended not to read closely. This is a design challenge.

Outcome


 * We want to build Concept A for mobile, but absorbing some of the best parts of Concept B's design. These are the reasons why:
 * User tests did not show advantages to Concept B.
 * Concept A gives more exposure to rest of editing experience.
 * Concept A will be more easily adapted to an “entry point in reading experience”: in addition to users being able to find tasks in a feed on their homepage, perhaps we could let them check to see if suggestions are available on articles as they read them.
 * Concept A was generally preferred by community members who commented on the designs, with the reason being that it seemed like it would help users understand how editing works in a broader sense.
 * We still need to design and test for desktop.

Ideas

The team had these ideas from watching the user tests:


 * Should we consider a “sandbox” version of the feature that lets users do a dry run through an article for which we know the “right” and “wrong” answers, and can then teach them along the way?
 * Where and when should we put the clear door toward other kinds of editing?  Should we have an explicit moment at the end of the flow that actively invites them copyedit or do another level task?
 * It’s hard to explain the rules of adding a link before they try the task, because they don't have context. How might we show them the task a little bit, before they read the rules?
 * Perhaps we could onboard the users in stages?  First they learn a few of the rules, then they do some links, then we teach them a few more pointers, then they do more links?
 * Should users have a cooling-off period after doing lots of suggestions really fast, where we wait for patrollers to catch up, so we can see if the user has been reverted?

Desktop mockups: October 2020
After designing, testing, and deciding on Concept A for mobile users, we moved on to thinking about desktop users. We again have the same question around Concepts A and B. The links below open interactive prototypes of each, which we are using for user testing.


 * Concept A: the structured task takes place at the article, in the editor, using some of the existing visual editor components. This gives users greater exposure to the editing context and may make it more likely that they explore other kinds of editing tasks.
 * Concept B: the structured task takes place on the newcomer homepage, essentially embedding the compact mobile experience into the page. Because the user doesn't have to leave the page, this may encourage them to complete more edits. They could also see their impact statistics increase as they edit.

We are user testing these designs during the week of October 23. See below for mockups showing the main interaction in each concept.

Outcome

The results of the desktop user tests led us to decide on Concept A for desktop for many of the same reasons we chose Concept A for mobile. The convenience and speed of Concept B did not outweigh the opportunity for Concept A to expose newcomers to more of the editing experience.

Terminology
"Add a link" is a feature in which human users interact with an algorithm. As such, it is important that user have a strong understanding that suggestions come from an algorithm and that they should be regarded with skepticism. In other words, we want the users to understand that their role is to evaluate the algorithm's suggestion and not to trust it to much. Terminology (i.e. the words we use to describe the algorithm) play an important role in building that understanding.

At first, we planned to use the terms "artificial intelligence" and "AI" to refer to the algorithm, but we eventually decided to use the term "machine". This may be a practice that gets adopted more broadly as multiple teams build more structured tasks that are backed by algorithms. Below is how we thought about this decision.

Background

As we build experiences that incorporate augmentation, we are thinking about the terminology to use when referring to suggestions that come from automated systems. If possible, we want to make a smart choice at the outset, to minimize changes and confusion later. For instance, we are looking at sentences in the feature like these:


 * "Suggested links are machine-generated, and can be incorrect."
 * "Links are recommended by machine, and you will decide whether to add them to the article."

Objectives

We want the terms we use to satisfy these objectives.


 * Transparency: users should understand where recommendations come from, and we should be being honest with them.
 * Human-in-the-loop: users should understand that their contributions improve recommendations in the future.
 * Usability: copy should help users complete the tasks, not confuse or burden them with too much information.
 * Consistency: we should use the same copy as much as possible to lower cognitive load.

Terms we considered Methods and findings


 * User testing: the Growth team tested "add a link" in English using the terms "artificial intelligence" and "AI". We found that users understood the term well and that English-speaking users understood that they should regard the output of AI with skepticism.
 * Experts: we spoke to WMF experts in the fields of artificial intelligence and machine learning. They explained that the link recommendation is not truly "AI", in the way that the term is used in the industry today. They explained that by using that term, we may be over-inflating our work and giving users a false sense of the intelligence of the algorithm. Experts preferred the term "machine", as it would accurately describe the link recommendation algorithm as well as be broad enough to describe almost any other kind of algorithm we might use for structured tasks.
 * Multi-lingual community members: we spoke to about seven multilingual colleagues and ambassadors about the terms that would make the most sense in their languages. Not all languages have a short acronym for "AI"; many have long translations. The consensus was that "machine" made good sense in most languages and would be easy to translate.

Result

We are going to use the term "machine" to refer to the link recommendation algorithm, e.g. "Suggested links are machine-generated". See screenshots below to see one of the places where the terminology changed based on this decision.

Hypotheses
The “add a link” workflow structures the process of adding wikilinks to a Wikipedia article, and assists the user with artificial intelligence to point out the clearest opportunities for adding links. Our hypothesis with the “add a link” workflow is that such a structured editing experience will lower the barrier to entry and thereby engage more newcomers, and more kinds of newcomers than an unstructured experience. We further hypothesize that newcomers with the workflow will complete more edits in their first session, and be more likely to return to complete more.

Below are the specific hypotheses we seek to validate. These govern the specifics around which data we'll collect and how we'll analyze it.


 * 1) The "add a link" structured task increases our core metrics of activation, retention, and productivity.
 * 2) “Add a link” edits are more likely to be successful than unstructured suggested edits, meaning that a user completes the task and saves the edit. They are also more likely to be constructive, meaning that the edit was not reverted, than unstructured suggested edits.
 * 3) Users seem to understand this task more than unstructured tasks.
 * 4) Users who start with "add a link" will move on to other kinds of tasks, instead of staying siloed (the latter being a primary community concern).
 * 5) The perceived quality of the link recommendation algorithm will be high, both from the users who make "add a link" edits and the communities who review those edits.
 * 6) Users who get “add a link” and who primarily use/edit wikis on mobile see a larger increase in the effects on retention and productivity relative to desktop users.

Experiment
A randomly selected half of users who get the Growth features will get "add a link" tasks, and the other randomly selected half will get unstructured link tasks. We prefer to give users maximum exposure to these tasks and will therefore not give these users any copyedit tasks by default. In other words, for the purposes of this experiment, we’ll change the default difficulty filters from “links” and “copyedit” to just “links”. For wikis that don’t have unstructured link tasks, all those users get “add a link” and in that case we’ll exclude that wiki from the experiment.

We plan to continue to have a Control group that does not get access to the Growth features, which is a randomly selected 20% of new registrations.


 * Group A: users get “add a link” as their only default task type.
 * Group B: users get unstructured link task as their only default task type.
 * Group C: control (no Growth features)

The experiment will run for a limited time, most likely between four to eight weeks. In practice the experiment will start with our four pilot wikis. After two weeks, we will analyze the leading indicators below to decide whether to extend the experiment to the rest of the Growth wikis.

Leading Indicators and Plan of Action
We are at this point fairly certain that Growth features are not detrimental to the wiki communities. That being said, we also want to be careful when experimenting with new features. Therefore, we define a set of leading indicators that we will keep track of during the early stages of the experiment. Each leading indicator comes with a plan of action in case the defined threshold is reached, so that the team knows what to do.

Analysis and Findings
We collected data on usage of Add a Link from deployment on May 27, 2021 until June 14, 2021. This dataset excluded known test accounts, and does not contain data from users who block event logging (e.g. through their ad blocker).

This analysis categorizes users into one of two categories based on when they registered. Those who registered prior to feature deployment on May 27, 2021 are labelled "pre-deployment", and those who registered after deployment are labelled "post-deployment". We do this because users in the "post-deployment" group are randomly assigned (with 50% probability) into either getting Add a Link or the unstructured link task. Users in the "pre-deployment" group have the unstructured link task replaced by Add a Link. By splitting into these two categories, we're able to make meaningful comparisons between Add a Link and the unstructured link task, for example when it comes to revert rate.

Revert rate: We use edit tags to identify edits and reverts, and reverts have to be done within 48 hours of the edit. The latter is in line with common practices for reverts.

For the post-deployment group, a Chi-squared test of proportions finds the difference in revert rate to be statistically significant ($$\chi^2=16.5, df=1, p \ll 0.001$$). This means that the threshold described in the leading indicator table is not met.

Rejection rate: We define an "edit session" as reaching the edit summary or skip all dialogue, at which point we count the number of links that were accepted, rejected, or skipped. Users can reach this dialogue multiple times, because we think that choosing to go back and review links again is a reasonable choice.

The threshold in the leading indicator table was a rejection rate of 30%, and this threshold has not been met.

Over-acceptance rate: This was not part of the original leading indicators, but we ended up checking for it as well in order to understand whether users were clicking "accept" on all the links and saving those edits. We reuse the concept of an "edit session" from the rejection rate analysis, and count the number of users who only have sessions where they accepted all links. In order to understand whether these users make many edits, we measure this for all users as well as for those with five or more edit sessions. In the table below, the "N total" column shows the total number of users with that number of edit sessions, and "N accepted all" the number of users who only have edit sessions where they accepted all suggested links.

We find that some users only have sessions where they accepted all links, but these users do not typically continue to make Add a Link edits. Instead, users who make additional edits start rejecting or skipping links as needed.

Task completion rate: We define "starting a task" as having an impression of "machine suggestions mode". In other words, the user is loading the editor with an Add a Link task. "Completing a task" is defined as clicking to save an edit, or confirming that all suggested links were skipped.

The threshold defined in the leading indicator table is "lower than 75%", and this threshold has been met. In this case, we're planning to do follow-up analysis to understand more about the tasks, e.g. if they had a low number of suggested links, or if this happens on specific wikis or platforms.

Rejection Reasons
We've analyzed data on why users reject suggested links, focusing on newcomers to help us understand how they learn what constitutes good links in Wikipedia. In this analysis, we used rejections from January and February 2022, and restricted it to actions made within 7 or 28 days since registration. There was no significant difference in patterns between the two, and the data reported here uses the 28 day window. The data was split by wiki, platform (desktop or mobile) and bucketed by the number of Add a Link edits the user had made. We used a logarithmic bucketing scheme with 2 as the base, because that gives us a fair number of buckets early in a user's life while at the same time being easy to understand since the limits double each time.

The distribution of these reasons is generally the same across all wikis, platforms, and number of Add a Link edits made. For some combinations of these features, we run into the issue of having few data points available (e.g. because some wikis lean strongly to usage of one platform) and that might result in a somewhat different distribution (e.g. just ones labelled "More/fewer words"). In general, we have a lot of data for users with few edits as that's what most users are.

One thing we do appear to see is that for some wikis the usage of "Other" decreases as the number of Add a Link edits made increases. We interpret this to mean that "Other" might be a catchall/safe category for less experienced users, and that as they become more experienced and confident in labelling a link they'll use a different category.

Link recommendation algorithm
See this page for an explanation of the link recommendation algorithm and for statistics around its accuracy. In short, we believe that users will experience an accuracy around 75%, meaning that 75% of the suggestions they get should be added. It is possible to tune this number, but the higher the accuracy is, the fewer candidate link we will be able to recommend. After the feature is deployed, we can look at revert rates to get a sense of how to tune that parameter.

For a detailed understanding of how the algorithm functions and is evaluated, see this research paper.

Link recommendation service backend
To follow along with engineering progress on the backend "add link" service, please see this page on Wikitech.

Deployment
On May 27, 2021, we deployed the first iteration of this task to our four pilot wikis: Arabic, Czech, Vietnamese, and Bengali Wikipedias. It is available to half of new accounts, as described above. All accounts created before the deployment will also have the feature available. After two weeks, we will analyze our leading indicators to determine if any quick changes need to be made. After about four weeks, we will use data and community feedback to determine whether and how to deploy the feature to more wikis.