User talk:PhotographerTom
PhotographerTom, you are invited to the Teahouse!
[edit]Hi PhotographerTom! Thanks for contributing to Wikipedia. Come join experienced editors at the Teahouse! The Teahouse is a space where new editors can get help from experienced editors. These editors have been around for a long time and have extensive knowledge about how Wikipedia works. Come share your experiences, ask questions, and get advice from experts. I hope to see you there! TheOriginalSoni (I'm a Teahouse host) This message was delivered automatically by your robot friend, HostBot (talk) 16:22, 29 October 2014 (UTC) |
VisualEditor News #3—2015
[edit]Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.
A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.
Recent improvements
[edit]Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.
The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).
The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).
Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).
The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.
The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.
Let's work together
[edit]- Share your ideas and ask questions at mw:VisualEditor/Feedback.
- The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
- If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
- If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)
Welcome to The Wikipedia Adventure!
[edit]- Hi PhotographerTom! We're so happy you wanted to play to learn, as a friendly and fun way to get into our community and mission. I think these links might be helpful to you as you get started.
-- 14:10, Friday, June 12, 2015 (UTC)
Mission 1 | Mission 2 | Mission 3 | Mission 4 | Mission 5 | Mission 6 | Mission 7 |
Say Hello to the World | An Invitation to Earth | Small Changes, Big Impact | The Neutral Point of View | The Veil of Verifiability | The Civility Code | Looking Good Together |
VisualEditor News #4—2015
[edit]Read this in another language • Local subscription list • Subscribe to the multilingual edition
Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.
Wikimania
[edit]The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.
Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.
For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).
For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).
We published some graphs showing the effect of the event on the Translathon page. Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.
Recent improvements
[edit]Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.
Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top.
In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.
Future changes
[edit]The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.
On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.
Let's work together
[edit]- Share your ideas and ask questions at Wikipedia:VisualEditor/Feedback.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
- If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
- Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
- The design research team wants to see how real editors work. Please sign up for their research program.
- The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact Elitre directly, so that she can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 00:01, 8 August 2015 (UTC)
PHP MediaWiki bots
[edit]Take a look at Wikipedia:Peachy. --Bamyers99 (talk) 19:50, 28 August 2015 (UTC)
- Thank you! --PhotographerTom (talk) 19:59, 28 August 2015 (UTC)
VisualEditor update
[edit]- This note is only delivered to English Wikipedia subscribers of the visual editor's newsletter.
The location of the visual editor's preference has been changed from the "Beta" tab to the "Editing" section of your preferences on this wiki. The setting now says Temporarily disable the visual editor while it is in beta. This aligns en.wiki with almost all the other WMF wikis; it doesn’t mean the visual editor is complete, or that it is no longer “in beta phase” though.
This action has not changed anything else for editors: it still honours editors’ previous choices about having it on or off; logged-out users continue to only have access to wikitext; the “Edit” tab is still after the “Edit source” one. You can learn more at the visual editor’s talk page.
We don’t expect this to cause any glitches, but in case your account no longer has the settings that you want, please accept our apologies and correct it in the Editing tab of Special:Preferences. Thank you for your attention, Elitre (WMF) -16:32, 7 October 2015 (UTC)
VisualEditor News #5—2015
[edit]Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements
[edit]Educational features: The first time you use the visual editor, it now draws your attention to the Link and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.
Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.
Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Insert Images and media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.
Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use the visual editor on any size of device. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.
Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227 and T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.
On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.
Future changes
[edit]You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, similar to the system already used on the mobile website. The "Edit" tab will open whichever editing environment you used last time.
Let's work together
[edit]- Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page uses Flow for discussions.
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
- Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
- The weekly task triage meetings are open to volunteers. Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.
If you can't read this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
— Whatamidoing (WMF) 04:15, 30 October 2015 (UTC)
VisualEditor News #6—2015
[edit]Read this in another language • Subscription list
Since the last newsletter, the VisualEditor Team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.
Recent improvements
[edit]You can switch from the wikitext editor to the visual editor after you start editing.
The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.
Future changes
[edit]The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, like the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Editing tab of Special:Preferences in the drop-down menu about "Editing mode:".
The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.
In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)
Testing opportunities
[edit]- Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
- Remember my last editor,
- Always give me the visual editor if possible,
- Always give me the source editor, and
- Show me both editor tabs. (This is the current state for people using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
- Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Whatamidoing (WMF), 00:54, 24 December 2015 (UTC)
VisualEditor News #1—2016
[edit]Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.
Recent changes
[edit]You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.
Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.
You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.
The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.
Future changes
[edit]The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Editing tab of Special:Preferences:
- Remember my last editor,
- Always give me the visual editor if possible,
- Always give me the source editor, and
- Show me both editor tabs. (This is the state for people using the visual editor now.)
The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.
The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. The developers would like to know how well the visual editor works in your language. They particularly want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect the following languages: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic and others.
Let's work together
[edit]- Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
- Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Language engineer David Chan needs help from people who often type in these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Report your results on wiki (Korean – Japanese – all languages).
- Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.
If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thanks!
– Whatamidoing (WMF) 17:47, 25 February 2016 (UTC)
Do you want one Edit tab, or two? It's your choice
[edit]The editing interface will be changed soon. When that happens, editors who currently see two editing tabs – "Edit" and "Edit source" – will start seeing one edit tab instead. The single edit tab has been popular at other Wikipedias. When this is deployed here, you may be offered the opportunity to choose your preferred appearance and behavior the next time you click the Edit button. You will also be able to change your settings in the Editing section of Special:Preferences.
You can choose one or two edit tabs. If you chose one edit tab, then you can switch between the two editing environments by clicking the buttons in the toolbar (shown in the screenshots). See Help:VisualEditor/User guide#Switching between the visual and wikitext editors for more information and screenshots.
There is more information about this interface change at mw:VisualEditor/Single edit tab. If you have questions, suggestions, or problems to report, then please leave a note at Wikipedia:VisualEditor/Feedback.
Whatamidoing (WMF) 19:22, 11 April 2016 (UTC)
Editing News #2—2016
[edit]Editing News #2—2016 Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the VisualEditor team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.
Recent changes
[edit]The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.
The single edit tab feature combines the "Edit" and "Edit source" tabs into a single "Edit" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Editing" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.
Future changes
[edit]The "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.
The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.
The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)
The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.
Let's work together
[edit]- Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
- Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!
Whatamidoing (WMF) (talk), 21:09, 30 June 2016 (UTC)
New newsletter for Notifications
[edit]Hello
You are subscribing to the Notifications newsletter on English Wikipedia.
That newsletter is now replaced by the monthly and multilingual Collaboration team newsletter, which will include information and updates concerning Notifications but also concerning Flow and Edit Review Improvements.
Please subscribe!
All the best, Trizek (WMF) (talk) 10:51, 29 September 2016 (UTC)
Editing News #3—2016
[edit]Read this in another language • Subscription list for this multilingual newsletter • Subscribe or unsubscribe on the English Wikipedia
Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.
Recent changes
[edit]- You can now set text as small or big.[1]
- Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[2] A similar feature will display the first part of hidden HTML comments.[3]
- Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[4]
- At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department are adding more features to this area, like geoshapes. You can read more on MediaWiki.org.[5]
- The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[6] In the future, the "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.
- Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[7]
Future changes
[edit]The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.
The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.
Let's work together
[edit]Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 18:19, 14 October 2016 (UTC)
Editing News #1—2017
[edit]Read this in another language • Subscription list for this multilingual newsletter
Since the last newsletter, the VisualEditor Team has spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.
Recent changes
[edit]A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [8]
The team have added multi-column support for lists of footnotes. The <references />
block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [9]
Other changes:
- You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [10]
- The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [11]
- The Categories item has been moved to the top of the Page options menu (from clicking on the icon) for quicker access. [12] There is also now a "Templates used on this page" feature there. [13]
- You can now create
<chem>
tags (sometimes used as<ce>
) for chemical formulas inside the visual editor. [14] - Tables can be set as collapsed or un-collapsed. [15]
- The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [16]
- A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [17]
- There is a new keyboard shortcut for citations:
Control
+Shift
+K
on a PC, orCommand
+Shift
+K
on a Mac. It is based on the keyboard shortcut for making links, which isControl
+K
on a PC orCommand
+K
on a Mac. [18]
Future changes
[edit]- The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of
<ref>
tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [19] - The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding
&ooui=1
to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [20] - The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors. See a list of editing tools on mediawiki.org if you are uncertain which one you use. [21]
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! User:Whatamidoing (WMF) (talk) 19:19, 9 May 2017 (UTC)
Editing News #1—2018
[edit]Read this in another language • Subscription list for the English Wikipedia • Subscription list for the multilingual edition
Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.
Recent changes
[edit]- The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
- The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [22]
- Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [23]
- The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time. It is very popular and useful to editors, although it can be tricky for admins to set up. Other wikis can have this service, too. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
Let's work together
[edit]- The team is planning a presentation about editing tools for an upcoming Wikimedia Foundation metrics and activities meeting.
- Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
- The
<references />
block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. This has already been enabled at the English Wikipedia. If you want columns for a long list of footnotes on this wiki, you can use either<references />
or the plain (no parameters){{reflist}}
template. If you edit a different wiki, you can request multi-column support for your wiki. [24] - If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
—User:Whatamidoing (WMF) (talk) 23:15, 28 February 2018 (UTC)
Editing News #2—2018
[edit]Read this in another language • Subscription list for this multilingual newsletter • Subscription list on the English Wikipedia
Did you know?
Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.
Recent changes
[edit]- The Editing team has published an initial report about mobile editing.
- The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
- The Reading team is working on a separate mobile-based contributions project.
- The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar. You may choose another editing tool in your editing preferences, local gadgets, or beta features.
- The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
- The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published. [25]
Let's work together
[edit]- The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
- The Community Wishlist Survey begins next week.
- If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
— Whatamidoing (WMF) (talk) 17:12, 1 November 2018 (UTC)
Editing News #1—July 2019
[edit]Read this in another language • Subscription list for this multilingual newsletter
Did you know?
Welcome back to the Editing newsletter.
Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.
Before talking about the team's recent releases, we have a question for you:
Are you willing to try a new way to add and change links?
If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.
Follow these instructions and share your experience:
Recent releases
[edit]The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team has recently launched two new features to improve the mobile visual editor:
- Section editing
- The purpose is to help contributors focus on their edits.
- The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
- Loading overlay
- The purpose is to smooth the transition between reading and editing.
Section editing and the new loading overlay are now available to everyone using the mobile visual editor.
New and active projects
[edit]This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.
- Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲Try Edit Cards.
- Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
- Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
- Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.
Looking ahead
[edit]- Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to them about how editing can be improved.
- Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.
Learning more
[edit]The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.
PPelberg (WMF) (talk) and Whatamidoing (WMF) (talk) 21:25, 15 July 2019 (UTC)
Editing News #2 – Mobile editing and talk pages – October 2019
[edit]Read this in another language • Subscription list for this multilingual newsletter
Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.
Help
[edit]What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!
Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team would value your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.
Talk Pages
[edit]The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.
The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.
Mobile visual editor
[edit]The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.
- On 3 September, the Editing team released version 3 of Edit Cards. Anyone could use the new version in the mobile visual editor.
- There is an updated design on the Edit Card for adding and modifying links. There is also a new, combined workflow for editing a link's display text and target.
- Feedback: You can try the new Edit Cards by opening the mobile visual editor on a smartphone. Please post your feedback on the Edit cards talk page.
- In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
- One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
- New navigation: The buttons for moving forward and backward in the edit flow have changed.
- Seamless switching: an improved workflow for switching between the visual and wikitext modes.
- Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.
Wikimania
[edit]The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.
Looking ahead
[edit]- Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
- Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
- Measuring the impact of Edit Cards: The Editing team hopes to share results in November. This study asks whether the project helped editors add links and citations. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.
– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 16:51, 17 October 2019 (UTC)
Editing news 2020 #1 – Discussion tools
[edit]Read this in another language • Subscription list
The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.
The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.
- On 31 March 2020, the new reply tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
- The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
- an easy way to mention another editor ("pinging"),
- a rich-text visual editing option, and
- other features identified through user testing or recommended by editors.
To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.
– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk) 15:45, 13 April 2020 (UTC)
Editing news 2020 #2 – Quick updates
[edit]Read this in another language • Subscription list
This edition of the Editing newsletter includes information the Wikipedia:Talk pages project, an effort to help contributors communicate on wiki more easily. The central project page is on MediaWiki.org.
- Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing
@
. You can test the new features on the Beta Cluster. Some other wikis will have a chance to try the Beta Feature in the coming months. - New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
- New discussion tool: The Editing team is beginning work on a simpler process for starting new discussions. You can see the initial design on the project page.
- Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.
– Whatamidoing (WMF) (talk) 18:11, 15 June 2020 (UTC)
Editing news 2020 #3
[edit]Seven years ago this week, the Editing team made the visual editor available by default to all logged-in editors using the desktop site at the English Wikipedia. Here's what happened since its introduction:
- The 50 millionth edit using the visual editor on desktop was made this year. More than 10 million edits have been made here at the English Wikipedia.
- More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
- Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
- The proportion of all edits made using the visual editor has been increasing every year.
- Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.
- On 17 November 2019, the first edit from outer space was made in the mobile visual editor.
- In 2019, 35% of the edits by newcomers, and half of their first edits, were made using the visual editor. This percentage has been increasing every year since the tool became available.
Whatamidoing (WMF) (talk) 02:06, 3 July 2020 (UTC)
Editing news 2020 #4
[edit]Read this in another language • Subscription list for this newsletter
Reply tool
[edit]The Reply tool has been available as a Beta Feature at the Arabic, Dutch, French and Hungarian Wikipedias since 31 March 2020. The first analysis showed positive results.
- More than 300 editors used the Reply tool at these four Wikipedias. They posted more than 7,400 replies during the study period.
- Of the people who posted a comment with the Reply tool, about 70% of them used the tool multiple times. About 60% of them used it on multiple days.
- Comments from Wikipedia editors are positive. One said, أعتقد أن الأداة تقدم فائدة ملحوظة؛ فهي تختصر الوقت لتقديم رد بدلًا من التنقل بالفأرة إلى وصلة تعديل القسم أو الصفحة، التي تكون بعيدة عن التعليق الأخير في الغالب، ويصل المساهم لصندوق التعديل بسرعة باستخدام الأداة. ("I think the tool has a significant impact; it saves time to reply while the classic way is to move with a mouse to the Edit link to edit the section or the page which is generally far away from the comment. And the user reaches to the edit box so quickly to use the Reply tool.")[26]
The Editing team released the Reply tool as a Beta Feature at eight other Wikipedias in early August. Those Wikipedias are in the Chinese, Czech, Georgian, Serbian, Sorani Kurdish, Swedish, Catalan, and Korean languages. If you would like to use the Reply tool at your wiki, please tell User talk:Whatamidoing (WMF).
The Reply tool is still in active development. Per request from the Dutch Wikipedia and other editors, you will be able to customize the edit summary. (The default edit summary is "Reply".) A "ping" feature is available in the Reply tool's visual editing mode. This feature searches for usernames. Per request from the Arabic Wikipedia, each wiki will be able to set its own preferred symbol for pinging editors. Per request from editors at the Japanese and Hungarian Wikipedias, each wiki can define a preferred signature prefix in the page MediaWiki:Discussiontools-signature-prefix. For example, some languages omit spaces before signatures. Other communities want to add a dash or a non-breaking space.
New requirements for user signatures
[edit]- The new requirements for custom user signatures began on 6 July 2020. If you try to create a custom signature that does not meet the requirements, you will get an error message.
- Existing custom signatures that do not meet the new requirements will be unaffected temporarily. Eventually, all custom signatures will need to meet the new requirements. You can check your signature and see lists of active editors whose custom signatures need to be corrected. Volunteers have been contacting editors who need to change their custom signatures. If you need to change your custom signature, then please read the help page.
Next: New discussion tool
[edit]Next, the team will be working on a tool for quickly and easily starting a new discussion section to a talk page. To follow the development of this new tool, please put the New Discussion Tool project page on your watchlist.
Whatamidoing (WMF) (talk) 18:48, 31 August 2020 (UTC)
Editing news 2021 #1
[edit]Read this in another language • Subscription list for this newsletter
Reply tool
[edit]The Reply tool is available at most other Wikipedias.
- The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
- It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.
Research notes:
- As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
- There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[27]
- The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[28] Some of the remaining changes are automatic corrections for Special:LintErrors.
- A large A/B test will start soon.[29] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.
New discussion tool
[edit]The new tool for starting new discussions (new sections) will join the Discussion tools in Special:Preferences#mw-prefsection-betafeatures at the end of January. You can try the tool for yourself.[30] You can leave feedback in this thread or on the talk page.
Next: Notifications
[edit]During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.
–Whatamidoing (WMF) (talk) 01:02, 23 January 2021 (UTC)
Editing news 2021 #2
[edit]Read this in another language • Subscription list for this newsletter
Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.
The key results were:
- Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
- The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.
These results give the Editing team confidence that the tool is helpful.
Looking ahead
The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.
The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.
You can turn on "Discussion Tools" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.
00:27, 16 June 2021 (UTC)
Disambiguation link notification for June 27
[edit]Hi. Thank you for your recent edits. An automated process has detected that when you recently edited School of Rock, you added a link pointing to the disambiguation page Kevin Clark. Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)
It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 05:59, 27 June 2021 (UTC)
Growth Newsletter #19
[edit]Welcome to the nineteenth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
Structured tasks
[edit]- "Add a link" is the team's first structured task. It uses machine-learning to suggest wikilinks as easy edits for newcomers. It was deployed in May 2021 on four Wikipedias and then in July on eight more Wikipedias after we evaluated the initial results. So far, we've seen a high level of engagement from newcomers. Communities that have the feature suggested valuable ideas for improvement. We'll work on improvements and then contact more communities to deploy it.
- "Add an image" is the team's second structured task, currently in development. It is an editing task that suggests Commons images for unillustrated Wikipedia articles. We have conducted many community discussions and tests. Then, we've decided to build a first prototype. We'll first deploy it only to our pilot Wikipedias, to learn whether newcomers can be successful with the task. The project page contains links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. These prototypes have already been tested by newcomers, in English and Spanish.
News for mentors
[edit]- The Mentor dashboard is available at our pilot wikis: Arabic, Czech, and Bengali Wikipedias. It will soon be available at a few more volunteering wikis, as a test. [31]
- At wikis where the mentor dashboard is deployed, a new filter is available for mentors. Mentors can monitor their mentees' activity in Watchlist and RecentChanges, so they can help support their mentees' work. For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are not listed as mentors [32]
Community configuration
[edit]- Communities now have the ability to configure how Growth features behave on their own wikis. At Special:EditGrowthConfig, community members can add a list of volunteer mentors, alter the templates used for suggested edits, update help links, and more. This special page is editable by administrators and interface admins.
Scaling
[edit]- We are proud to announce that all Wikipedias now have the Growth features! Thank you to all the community members who helped the team build the features and bring them to their wikis. The only exception is Chinese Wikipedia (zh), for technical reasons. [33]
- The wikis that have Growth features deployed have been part of A/B testing since deployment, in which some newcomers did not receive the new features. Now, all of the newcomers on 280 of the smallest of those Wikipedias have the features. [34][35]
- A test is undergoing at English Wikipedia: 25% of newcomers receive the Growth features. The results from this test will be part of a discussion of how to proceed on that wiki.
- Now that Growth features are available at Wikipedia, the Growth team considers to extend them to other projects. Some Wikisource users have expressed some interest in getting Growth features. There is currently a discussion about implementing them on Wikisource.
News for communities
[edit]- Do you have questions about the Growth features? This translatable FAQ contains answers to the most common questions about the Growth team work.
- The Growth features were recently used in a test amongst Latin American donors to give donors the opportunity to learn to edit. You can see the results here.
- Interface translations are important for newcomers. Please help for your language, by translating or copyediting interface translations for the Growth features.
- Help:GettingStarted was a feature developed in 2013, which directed newcomers to articles that needed editing. We recently removed this feature from all wikis, because it has been replaced by the Growth features.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
18:36, 26 October 2021 (UTC)
Growth Newsletter #20
[edit]Welcome to the twentieth newsletter from the Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
Suggested edits
[edit]As of February, 300,000 suggested edits have been completed since the feature was first deployed in December 2019.
Add a link is the team's first structured task, deployed in May 2021. It has improved outcomes for newcomers. The team is now working on a second iteration based on community feedback and data analysis. Improvements will include: improved algorithmic suggestions, guardrails to prevent too many similar links to be added, and clearer encouragement for users to continue making edits. After adding these improvements, we will deploy this task to more Wikipedias.
Add an image is the second structured task built by our team. It was deployed in November 2021 to four pilot Wikipedias. This is a more challenging task for newcomers. However, it adds more value to articles (so far, over 1,000 images have been added). We are currently learning from communities and from the data on what is working well and what needs improvements. The project page contains links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. We will soon deploy this task to more Wikipedias as a test.
"Add a link" and "Add an image" now both have a limitation on how many of these tasks newcomers can do per day. It is meant to discourage careless newcomers from making too many problematic edits.
Positive reinforcement
[edit]Over the last two years, the Growth team has focused on building suggested edits: easy tasks for newcomers to start with. We have learned with this experience that these tasks help many newcomers to make their first edits. Now, the team is starting a new project : "positive reinforcement". Its goal is to make newcomers proud of their editing and to make them want to come back for more of them. With the positive reinforcement project, we are considering three kinds of features:
- Impact stats: give newcomers the ability to see how many people read the articles they edit.
- Leveling up: encourage newcomers to progress from easier tasks to harder tasks.
- Personalized praise: encourage mentors and other editors to "thank" and award newcomers for good work.
This project is just beginning, and we hope for community thoughts on the direction. We know that things can wrong if we offer the wrong incentives to newcomers, so we want to be careful. Please visit the talk page to help guide the project!
News for mentors
[edit]- The mentor dashboard is available at all wikis. It helps mentors see who their mentees are and keep track of their activity. It is automatically activated where a list of mentors has been created. If you need assistance to create a list of mentors, please contact us.
- The mentor dashboard has a new module: settings. It is now possible for mentors to define their status (active or away). They can specify the volume of questions they want to receive, and they can claim mentees in an easier way. It is also possible for mentors to quit, which will automatically reassign their mentees to other mentors.
- We are working on an ability for a mentee to opt-out (and back in) to having a mentor.
- Previously, in the table that displays mentees activity, the filters displayed all mentees, even the ones with zero edits or lots of edits. We have changed this so that only mentees with between 1 and 500 edits are visible by default. Mentors can change this value in their filters.
- We are currently working on a special page for mentors to sign-up.
Some wikis have created userboxes that mentors can display on the user pages. If your wiki has one, please link it to Wikidata!
Scaling
[edit]Previously, at most Wikipedias, only 80% of newcomers were getting the Growth features. This was done for experimentation, to have a control group. We have changed this setting. Now 100% of new accounts at all Wikipedias get the Growth features (except a few, kept as test wikis). We invite communities to update their onboarding documentation and tutorials. Please include the Growth features in it. To help you, we have created an help page that can be translated and adapted to your wiki.
How to help
[edit]Do you have questions about the Growth features? This translatable FAQ contains answers to the most common questions about the Growth team work. We regularly update it.
Interface translations are important for newcomers. Please help for your language, by translating or copyediting interface translations for the Growth features.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:12, 16 March 2022 (UTC)
Editing newsletter 2022 – #1
[edit]Read this in another language • Subscription list for the multilingual newsletter • Local subscription list
The New topic tool helps editors create new ==Sections== on discussion pages. New editors are more successful with this new tool. You can read the report. Soon, the Editing team will offer this to all editors at most WMF-hosted wikis. You can join the discussion about this tool for the English Wikipedia is at Wikipedia:Village pump (proposals)#Enabling the New Topic Tool by default. You will be able to turn it off in the tool or at Special:Preferences#mw-prefsection-editing-discussion.
The Editing team plans to change the appearance of talk pages. These are separate from the changes made by the mw:Desktop improvements project and will appear in both Vector 2010 and Vector 2022. The goal is to add some information and make discussions look visibly different from encyclopedia articles. You can see some ideas at Wikipedia talk:Talk pages project#Prototype Ready for Feedback.
23:14, 30 May 2022 (UTC)
Growth team newsletter #21
[edit]Welcome to the twenty-first newsletter from the Growth team!
New project: Positive reinforcement
[edit]- The Growth team started a new project: Positive reinforcement. We want newcomers to understand there is an interest in regularly editing Wikipedia, and we want to improve new editor retention.
- We asked users from Arabic, Bangla, Czech and French Wikipedia about their feedback. Some people participated at mediawiki.org as well.
- We summarized the initial feedback gathered from these community discussions, along with how we plan to iterate based on that feedback.
- The first Positive Reinforcement idea is a redesign of the impact module: incorporating stats, graphs, and other contribution information. This idea received the widest support, and we plan to start our work based on the design illustrated on the side.
- Please let us know what you think of this project, in any language.
For mentors
[edit]- We have worked on two new features, to inform them about the mentorship:
Scaling
[edit]- "Add a link" available at more wikis ― Add a link feature has been deployed to more wikis: Catalan Wikipedia, Hebrew Wikipedia, Hindi Wikipedia, Korean Wikipedia, Norwegian Bokmål Wikipedia, Portuguese Wikipedia, Simple English Wikipedia, Swedish Wikipedia, Ukrainian Wikipedia, Abkhazian Wikipedia, Achinese Wikipedia, Adyghe Wikipedia, Afrikaans Wikipedia, Akan Wikipedia, Alemannisch Wikipedia, Amharic Wikipedia, Aragonese Wikipedia, Old English Wikipedia, Syriac Wikipedia, Egyptian Arabic Wikipedia, Asturian Wikipedia, Atikamekw Wikipedia, Avaric Wikipedia, Aymara Wikipedia, Azerbaijani Wikipedia, South Azerbaijani Wikipedia. This is part of the progressive deployment of this tool to more Wikipedias. The communities can configure locally how this feature works.
- "Add an image" available at more wikis ― Add an image feature will be deployed to more wikis: Greek Wikipedia, Indonesian Wikipedia, Polish Wikipedia, Chinese Wikipedia. These communities will be able to configure locally how this feature works. [36]
Suggested edits
[edit]- Selecting topics ― We have created an "AND" filter to the list of topics at Special:Homepage. This way, newcomers can decide to select very specific topics ("Transportation" AND "Asia") or to have a broader selection ("Transportation" OR "Asia"). At the moment this feature is tested at pilot wikis.
- Changes for Add a link ― We have built several improvements that came from community discussion and from data analysis. They will be available soon at the wikis.
- Algorithm improvements ― The algorithm now avoids recommending links in sections that usually don't have links and for first names. Also, it now limits each article to only having three link suggestions by default (limited to the highest accuracy suggestions of all the available ones in the article).
- User experience improvements ― We added a confirmation dialog when a user exits out of suggestion mode prior to making changes. We also improved post-edit dialog experience and allow newcomers to browse through task suggestions from the post-edit dialog.
- Community configuration ― We allow communities to set a maximum number of links per article via Special:EditGrowthConfig.
- Future change for Add a link feature ― We will suggest underlinked articles in priority. [37]
- Patrolling suggested edits ― Some users at Arabic Wikipedia, Spanish Wikipedia, and Russian Wikipedia told us that "Add a link" and "Add an image" edits can be challenging to patrol. We are now brainstorming improvements to help address this challenge. We have already some ideas and we started some work to address this challenge. If you have any thoughts to add about the challenges of reviewing these tasks or how we should improve these tasks further, please let us know, in any language.
Community configuration
[edit]Communities can configure how the features work, using Special:EditGrowthConfig.
- Communities can set the maximum number of "add an image" suggested tasks a newcomer can complete daily. [38]
- Future change: allow communities to customize the "add a link" quality gate threshold easily, using Special:EditGrowthConfig. [39]
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
13:03, 5 July 2022 (UTC)
Editing news 2022 #2
[edit]Read this in another language • Subscription list for this multilingual newsletter
The new [subscribe] button notifies people when someone replies to their comments. It helps newcomers get answers to their questions. People reply sooner. You can read the report. The Editing team is turning this tool on for everyone. You will be able to turn it off in your preferences.
–Whatamidoing (WMF) (talk) 00:35, 26 August 2022 (UTC)
Growth team newsletter #22
[edit]Welcome to the twenty-second newsletter from the Growth team!
Newcomers tasks reach the 500,000 edits milestone — more data publicly available
[edit]As of the last week of June 2022, the newcomers of the world have completed over 500,000 newcomer tasks. In other words, newcomers have made over half a million Wikipedia edits via Growth’s “Suggested Edits” module.
- About 30% of those edits were completed on mobile devices.
- Usage continues to increase; in June 2022 almost 50,000 newcomer tasks were completed.
We have added some new data to Grafana. You can now check the number of edits and reverts by task types, or the number of questions asked to mentors. You can filter the data by wiki.
If you have any questions, or there is more data you want access to, please let us know.
Ongoing projects and explorations
[edit]We are continuing our work on our new project, Positive Reinforcement. User testing of initial Positive Reinforcement designs was just completed. Interviews were conducted in Arabic, English, and Spanish. The outcome has been published on the Positive Reinforcement page. We are now utilizing user testing feedback along with prior community feedback to iterate and improve designs.
We are exploring the idea of a Copy Edit structured task. We have tested copy edits in Wikipedia articles for arwiki, bnwiki, cswiki, eswiki (Growth pilot-wikis) and enwiki with two different methods: LanguageTool and Hunspell. We will share more details here and on the associated Copy Edit page once the evaluation is complete.
Add an image was utilized at GLAM events in Argentina, Mexico, and Chile. For an overview of what was learned from these events, read: #1Pic1Article I: how Latin American heritage experts added images to Wikipedia (in English).
Experiments analysis
[edit]Add a Link Experiment Analysis has been published. The most important points are:
- Newcomers who get the Add a Link structured task are more likely to be activated (i.e. make a constructive first article edit).
- They are also more likely to be retained (i.e. come back and make another constructive article edit on a different day).
- The feature also increases edit volume (i.e. the number of constructive edits made across the first couple weeks), while at the same time improving edit quality (i.e. the likelihood that the newcomer's edits aren't reverted).
Newcomer task edit type analysis has been published.
- Communities had expressed concern that newcomers whose initial edits were structured tasks wouldn’t go on to learn how to complete more difficult tasks. The Growth team data scientist conducted a Newcomer task edit type analysis to see if this was indeed the case.
- Results from analysis indicate that this likely isn’t a significant concern. More than 70% of users who start with the easy task "Add a link" also make another task type. Read the full analysis and methodology here.
News for mentors
[edit]A new system for the mentors list
The configuration of the mentors list will change over the next weeks. In the future, mentors will sign up, edit their mentor description and quit using Special:MentorDashboard. This new system will make the development of new features for mentors much easier.
At the moment, the mentor list is a simple page anyone can edit, unless it’s protected. With the new page, mentors will be able to edit only their own description, while administrators will be able to edit the entire mentors' list if needed.
The deployment will happen first at the pilot wikis, then at all wikis. Existing lists of mentors will be automatically converted, no action will be needed from the mentors. [40][41]
Mentors will be informed about the next steps soon, by a message posted on the talk page of existing Mentor lists.
Learn more about this new structured page on mediawiki.org.
A tip for mentors
Did you know that mentors can filter their mentees' changes at Special:MentorDashboard (and star the ones that require attention)? This feature helps to keep an eye on newcomers' edits, helping mentors to fix minor details, and encourage them if necessary.
And did you know that mentors have special filters to highlight their mentees' edits at Special:RecentChanges? Look for the following filters in RecentChanges: Your starred mentees, Your unstarred mentees.
Other improvements
Some improvements will be made to the mentor dashboard in the coming weeks:
- While we now offer some options for mentors to take a break, the option to quit mentoring was not easy to find. This will be improved. [42]
- Mentors at wikis using FlaggedRevisions will have a way to discover their mentees' pending edits. [43]
- Dashboard discovery for new mentors will be improved. [44]
Recent changes and fixed bugs
[edit]- We moved to a new Image Suggestions API. This new API will allow us to deploy Add an Image to more wikis. [45]
- Starting September 19, a few more wikis now offer Add an image to newcomers. These wikis are Greek Wikipedia, Polish Wikipedia, Chinese Wikipedia, Indonesian Wikipedia, Romanian Wikipedia. [46]
- Add an image has been disabled for a few days due to technical issue. "Add an image" added a blank line instead of an image. This has been fixed. [47]
- In order to know if Special:EditGrowthConfig is used by communities, we now instrument page loads and saves of configuration. [48]
Have a question? A suggestion?
[edit]Please let us know! You can also read our FAQ page.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
17:18, 21 September 2022 (UTC)
Growth team newsletter #23
[edit]Welcome to the twenty-third newsletter from the Growth team!
Highlights
[edit]- Mentorship: We released the new structured mentor list to all wikis. This change makes mentorship easier to setup, manage and use.
- Positive reinforcement: An improved impact module is available for testing.
Positive reinforcement: an improved impact module to test
[edit]The goal of the Growth team is to encourage newcomers to try editing for the first time, and encourage them to keep editing. We want to increase newcomers' motivation by showing them how impactful their edits are.
Newcomers have access to an impact module; you can find yours at Special:Impact. The revised impact module provides new editors with more context about their impact. It will display the number of edits, the number of thanks received, the last time they edited, the number of consecutive days they edited, and the number of views for the articles they edited.
This module will soon be available at our pilot wikis starting December 1. You can already test this new module at Beta Wikipedia. For safety reasons, do not use your regular account and password at Beta wiki. Create a new, specific account for this wiki, with a different password.
Structured tasks: improvements based on patroller feedback
[edit]After the deployment of Structured tasks, we received feedback from various communities regarding how patrollers of recent changes were feeling overwhelmed by an increase in edits to check, and how some edits were poor quality or of poor relevance.
We made several improvements based on the feedback we received. Several points of improvement have already been addressed:
- Patroller fatigue:
- By default, newcomers can complete up to 25 "add a link" tasks and 25 "add an image" tasks per day. If patrollers are overburdened, each community can use Special:EditGrowthConfig to lower that limit.
- Quality of edits: what constitutes a "quality edit" is not a well defined concept. We initiated a discussion and summarized our findings. We also worked on the following improvements:
- Add a Link
- Underlinked articles are now prioritized, so it's less likely that newcomers are adding links to articles that are already have a lot of links.
- The confidence score was increased, so suggestions are more likely to be accurate.
- The default number of suggested links per article has been lowered to 3. This can be changed at Special:EditGrowthConfig. Communities can also exclude articles containing certain templates or categories from being suggested.
- Add an Image
- Lists will no longer receive "add an image" suggestions.
- Disambiguation pages will no longer receive "add an image" suggestions.
- We have many further improvements we plan to make to "add an image" in early 2023. [49]
- Add a Link
The Positive Reinforcement project will also address some of the concerns around encouraging newcomers to progress to higher value edits. The Growth team will soon work on strategies geared at "Leveling up" newcomers so they progress from easy to more difficult tasks.
Recent changes
[edit]- All Wikipedias now have the same onboarding experience. Previously, at a few wikis, 20% of new accounts didn't get the Growth features when they created their account. These 20% of new accounts were used as a control group, in order to know if the Growth features were changing newcomers' behavior. Experiments have shown that Growth features improve activation and retention, and as we want to provide the same onboarding experience at all Wikipedias, we have decided to remove the control groups. We will utilize control groups when testing new features, and German Wikipedia keeps a control group at their request. [50]
- The quality score for "add a link" suggestions will change. We will suggest less links for each article, but they will be more accurate. We will first deploy it at our pilot wikis, and then to all other wikis where this feature is available. [51][52]
- Growth's features FAQ has been updated and expanded. This page centralizes all the information about Growth features. We invite you to read it, and, if you can, to translate it.
News for mentors
[edit]- All Wikipedias can now setup and manage a mentorship program in an easier way.
- We changed the process to make it more reliable, easier to improve and easier to use.
- Wikipedias where mentorship hasn't been enabled yet can turn mentorship on following a new process. When done, mentors can sign-up by visiting
Special:MentorDashboard
. - Wikipedias where the list of mentors already existed have been converted to the new system.
- A new special page —
Special:ManageMentors
— now displays the list of mentors. This page can be transcluded on any other page. There are also new processes to signup as a mentor or to quit mentorship, and we improved community mentorship management.
- The Mentor dashboard's "Your mentees" module will have a new footer, called "Recent changes by your mentees". This footer will include a link to Recent changes, where mentors can see only edits made by their own mentees. [53]
Deployments
[edit]- Add a link has been deployed to a 5th round of wikis. [54]
Improving this newsletter
[edit]We plan to have a more regular newsletter, every two months. We also want to know if the current format suits you! Let us know what you like, what you like less and your suggestions of improvements: leave us a comment, in your preferred language.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
20:57, 29 November 2022 (UTC)
Growth team newsletter #24
[edit]Welcome to the twenty-fourth newsletter from the Growth team!
Newcomer experience projects
[edit]The Growth team partnered with other WMF teams to conduct several experiments around increasing account creation and new editor retention. Results from four of these experiments are now available:
- Thank you pages & banners - Encourage donors to create accounts through thank you pages and banners.
- Marketing experiment - Run ads on-wiki and off-wiki to see how this impacts account activation.
- "Add an image" GLAM events - Host GLAM events that focus on using the "Add an image" tool.
- Welcome emails - Experiment sending welcome emails to newly created accounts.
Newcomer tasks
[edit]- Several communities suggested improving "add a link", by suggesting underlinked articles first. We released this change to Growth pilot wikis. We will review the data and collect feedback before considering releasing it to more wikis. [55]
- The deployment of the "add a link" to all Wikipedias is still in progress. Suggested links use a prediction model, which has to be trained. The deployments will resume after we finish training all models. [56]
Mentorship
[edit]- When someone wants to signup as a mentor, they are now informed if they don't meet the defined criteria. [57]
- Workshop hosts asked us to have workshop attendees assigned to them. They can soon use a custom URL parameter. This way, workshop hosts will continue mentoring the event's attendees after the workshop. It will be available in February. [58]
- Have you considered to help new editors on your wiki, by signing up to be a Mentor?
- Please visit Special:MentorDashboard to check on the conditions to be a mentor, and sign up.
- If your wiki does not have Mentorship enabled, consider setting it up. The Growth team can provide advice and assist as needed. Please ping Trizek (WMF) for assistance.
Other news
[edit]- In Special:SpecialPages, Growth experiments now have their own section. [59]
- This newsletter will have a new publication period, 6 times a year: January, March, May, July, September, November.
Translations
[edit]- Newsletter translation: We are looking for translators for this newsletter. If you are interested and have the needed English language proficiency to assist, then please add your name to this list. You will receive an invite on your talk page to translate the newsletter when it is ready.
- Interface translation: You can also help by translating the interface, or reviewing translations to make them more inclusive. Interface translations are hosted at translatewiki.net.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.• Help with translations
14:44, 31 January 2023 (UTC)
Editing news 2023 #1
[edit]Read this in another language • Subscription list for this newsletter
This newsletter includes two key updates about the Editing team's work:
- The Editing team will finish adding new features to the Talk pages project and deploy it.
- They are beginning a new project, Edit check.
Talk pages project
The Editing team is nearly finished with this first phase of the Talk pages project. Nearly all new features are available now in the Beta Feature for Discussion tools.
It will show information about how active a discussion is, such as the date of the most recent comment. There will soon be a new "Add topic" button. You will be able to turn them off at Special:Preferences#mw-prefsection-editing-discussion. Please tell them what you think.
An A/B test for Discussion tools on the mobile site has finished. Editors were more successful with Discussion tools. The Editing team is enabling these features for all editors on the mobile site.
New Project: Edit Check
The Editing team is beginning a project to help new editors of Wikipedia. It will help people identify some problems before they click "Publish changes". The first tool will encourage people to add references when they add new content. Please watch that page for more information. You can join a conference call on 3 March 2023 to learn more.
–Whatamidoing (WMF) (talk) 18:19, 22 February 2023 (UTC)
Growth team newsletter #25
[edit]Welcome to the twenty-fifth newsletter from the Growth team! Help with translations
Celebrations
[edit]Leveling up release
- We released Leveling up features to our pilot wikis on March 22 for an initial A/B test.
- In this test, we use post-edit dialogs (pop-ups shown after publishing an edit) and notifications to encourage new editors to try new types of newcomer-friendly suggested edits.
- We are closely monitoring the short term impact of this feature as well as the longer term effect on newcomer productivity and retention. If the experiment shows positive results, we will release this feature to more wikis.
5,000+ images added via the newcomer task in February
- In February 2023, 5,035 images were added via the newcomer “add an image” feature (on all wikis where available); 155 were reverted.
- Since the feature “add an image” was launched: 36,803 images have been added; 2,957 images were reverted.
Recent changes
[edit]- Add a link
- Community Ambassadors completed an initial evaluation that confirmed that prioritizing underlinked articles resulted in better article suggestions. We then evaluated the change on Growth pilot wikis, and results suggest that more newcomers are successfully completing the task and experiencing fewer reverts. We have now deployed the new prioritization model to all wikis with "add a link" enabled. [60][61]
- We continue the deployment of "add a link" to more wikis. These changes are regularly announced in Tech News. To know if newcomers at your wiki have access to this feature, please visit your Homepage.
- The Impact module was deployed on our pilot wikis, where we conducted an A/B test. We published initial findings, and a data scientist is now completing experiment analysis. [62]
- Donor Thank you page experiment – Donors land on a “thank you” page after donation, and that landing page now includes a call to action to try editing: Example Thank you page in French. This promising feature is tested at several Wikipedias (French Wikipedia, Italian Wikipedia, Japanese Wikipedia, Dutch Wikipedia, Swedish Wikipedia).
- Growth features are now the default experience on both test.wikipedia.org and test2.wikipedia.org. You can test our features there.
Upcoming work
[edit]- Add an image – We plan to offer section-level image suggestions as a structured task for newcomers.
- IP Editing: Privacy Enhancement and Abuse Mitigation – We will support this project for all Growth Team maintained products and extensions that may be affected by IP Masking. [66]
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
13:10, 1 April 2023 (UTC)
Growth team newsletter #26
[edit]Welcome to the twenty-sixth newsletter from the Growth team! Help with translations
One million Suggested Edits
[edit]We passed the 1 million Suggested edits milestone in late April!
- The Suggested edits feature (AKA Newcomer tasks) increase newcomer activation by ~12%, which flows on through to increased retention. (source)
- Suggested edits increase the number of edits newcomers complete in their first two weeks and have a relatively low revert rate. (source)
- Suggested edits are available on all Wikipedia language editions.
- Newer Suggested edits, like Add a link and Add an image, aren’t yet deployed to all wikis, but these structured tasks further increase the probability that newcomers will make their first edit. (source)
Positive reinforcement
[edit]Positive reinforcement aims to encourage newcomers who have visited our homepage and tried Growth features to keep editing.
- The new Impact module was released to Growth pilot wikis in December 2022, and we are now scaling the feature to another ten wikis. [67]
- The Leveling up features are deployed at our pilot wikis.
- The Personalized praise features were deployed at our pilot wikis on May 24. Mentors at pilot wikis will start to receive notifications weekly when they have “praise-worthy” mentees. Mentors can configure their notification preferences or disable these notifications.
Add an image
[edit]- We are creating a new section-level variation of the “add an image” task. We have tested the accuracy of suggestions, and the development of this new task is well-underway. [68]
Other updates
[edit]- We are progressively releasing Add a link to more wikis. [69]
- After adding Thanks to Recent Changes, Watchlist and Special:Contributions, we investigated Thanks usage on the wikis. There is no evidence that thanks increased after the feature was added on more pages.
- We helped with code review for the 2023 Community Wish to add Notifications for user page edits. [70]
- We have been attending several community events, that we documented in our Growth’s Community events report.
What's next for Growth?
[edit]- We shared an overview of Growth annual planning ideas, and have started community discussion about these potential projects. We would love to hear your feedback on these ideas!
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
15:14, 29 May 2023 (UTC)
Growth team newsletter #27
[edit]Welcome to the twenty-seventh newsletter from the Growth team! Help with translations
Annual plan for Growth
[edit]We shared our annual plan, for the period July 2023 - June 2024.
Our first project of the year will be Community configuration 2.0, which helps editors with extended rights transparently and easily configure important on-wiki functionality.
After we finish work on Community configuration 2.0, we will hope to fit in one of the following projects:
- Article creation: This project aims to provide new editors with better guidance and guardrails in the article creation process, with the intention of lightening the load of new page reviewers.
- Non-editing participation: This project aims to create low-risk ways for readers to participate in Wikipedia with the intention of funneling more readers into contributing to the Wikimedia movement.
Please let us know what you think about these projects on the related talk page, or Growth's annual plan talk page.
Suggested edits
[edit]We released a new Section-level “add an image” structured task to Growth pilot wikis (Arabic, Bengali, Czech, and Spanish). This task was part of the Structured Data Across Wikipedia project. We are monitoring the edits made, and we look for community feedback as well.
Suggested Edits are now receiving topic predictions via the new Language-Agnostic Topic Classification. This change affects non-English Wikipedia wikis. It will ensure newcomers receive a greater diversity of task recommendations. Before, as this feature was a test, English Wikipedia was used to select topics. The change is gradual as lists of topics are refreshed when they become empty. The Research team will evaluate the impact in a few months. [71]
Starting on August 1, a new set of Wikipedias will get "Add a link": Georgian Wikipedia, Kara-Kalpak Wikipedia, Kabyle Wikipedia, Kabardian Wikipedia, Kabiyè Wikipedia, Kikuyu Wikipedia, Kazakh Wikipedia, Khmer Wikipedia, Kannada Wikipedia, Kashmiri Wikipedia, Colognian Wikipedia, Kurdish Wikipedia, Cornish Wikipedia, Cornish Wikipedia.
Mentorship
[edit]The Growth team provides dedicated features to establish a mentorship program for newcomers. Every newcomer gets a volunteer mentor who provides encouragement and answers questions. Communities can set up or join this mentorship system by visiting Special:ManageMentors. This mentorship system is configurable by the community at Special:EditGrowthConfig.
More communities have implemented mentorship. A Wikimedia Foundation data scientist will be looking at the impact of Mentorship. We will look at the impact on Spanish and English Wikipedia. [72]
The Growth team will also host a Mentoring new editors on Wikipedia session at Wikimania 2023 in Singapore. Workshop attendees will help brainstorm improvements to Growth’s mentorship features.
Positive reinforcement
[edit]We will share more complete experiment analysis for all the three parts of the Positive reinforcement project soon. At the moment, the new Impact module, Leveling up, and Personalized praise are still being A/B tested on the Growth team's pilot wikis.
In the meantime, initial leading indicators for the Personalized praise project have been published. Although this is still a relatively small sample, results seem healthy. They show that Mentors are indeed receiving notifications and clicking through to view their praise-worthy mentees.
Growth contributes to IP Editing migration
[edit]The Growth team is currently focusing on IP Editing: Privacy Enhancement and Abuse Mitigation. It is a project that touches many different Wikimedia Foundation teams. The Growth team will focus on temporary accounts through two main points:
- the user experience of a logged-out user, that switches to a temporary account,
- change Growth-owned extensions and features, so that they work as expected with temporary accounts. [73]
Community Configuration 2.0
[edit]We are still in the early planning stage of the Community Configuration 2.0 project:
- We are gathering internal Wikimedia Foundation teams' needs, so as community feedback. [74]
- We have started to investigate design improvements. [75]
- We are also reviewing similar tools that are part of other products. [76]
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
12:42, 1 August 2023 (UTC)
Growth team newsletter #28
[edit]Welcome to the twenty-eighth newsletter from the Growth team! Help with translations
Community configuration 2.0
[edit]- Community Configuration 2.0 is a feature that will enable Wikimedia communities to easily customize and configure features to meet their unique needs. This approach provides non-technical moderators with more independence and control over enabling/disabling and customizing features for their communities.
- Technical approach and associated tasks are detailed in this Epic task on Phabricator.
- Initial designs are drafted for two different approaches (see images). We will soon demo interactive prototypes to interested admins, stewards, and experienced editors (T346109). Please let us know if you have feedback on the design approach, or want to participate in prototype testing.
IP Masking
[edit]- The Growth team has been working on several updates to ensure Growth maintained features will be compatible with future IP Masking changes. This work has included code changes to: Recent Changes (T343322), Echo notifications (T333531), the Thanks extension (T345679) and Mentorship (T341390).
- Before December, the Growth team will initiate community discussions with the goal of migrating communities from Flow to DiscussionTools. This move aims to minimize the necessity for additional engineering work to make Flow compatible with IP Masking. (T346108)
Mentorship
[edit]- We assembled some resources for mentors at Mediawiki wiki. This resource page is translatable and will be linked from the mentor dashboard.
- We are working to resolve a bug related to mentors properly returning after being marked as "Away". (T347024)
- Half of newcomers at English Wikipedia get a mentor assigned to them. To ensure every newcomer receives mentorship, we need additional volunteer mentors at English Wikipedia to achieve a 100% coverage rate. We also encourage experienced users from other wikis to help newcomers at their own community.
Scaling Growth features
[edit]- We continue the deployment of the structured task "add a link" to all Wikipedias. We plan to scale the task to all Wikipedias that have link suggestions available by the end of 2023.
- We plan to scale the new Impact Module to all Wikipedias soon, but first we are investigating a bug with the job that refreshes the Impact Module data. (T344428)
- At some wikis, newcomers have access to the "add an image" structured task. This task suggests images that may be relevant to add to unillustrated articles. Newcomers at these wikis can now add images to unillustrated articles sections. (T345940) The wikis that have this task are listed under "Images recommendations" at the Growth team deployment table.
Other news
[edit]- We disabled the “add an image” task temporarily (T345188) because there was a failure in the image suggestions pipeline (T345141). This is now fixed.
- You can read a report about the Growth team’s representation at Wikimania in Singapore here. Growth team members presented two sessions at Wikimania Singapore.
- After a 2.5 years-long collaboration with Bangala Wikipedia, we have decided to start a collaboration with another wiki. Swahili Wikipedia is now a pilot wiki for Growth experiments.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
Trizek_(WMF) Talk 23:16, 16 October 2023 (UTC)
Growth team newsletter #29
[edit]Welcome to the twenty-ninth newsletter from the Growth team! Help with translations
Community Conversations
[edit]The Growth team will host its first community conversation Monday, 4 December (19:00 - 20:30 UTC). The topic for this meeting will be Mentorship.
This first meeting language will be English, but we plan to host conversations in other languages, and about other topics. Please visit the conversation page on-wiki for the details on how to join. You can also watch the page, or suggest ideas for upcoming conversations there.
Impact Module
[edit]At the beginning of November 2023, the Growth team deployed the New Impact Module to all Wikipedias. We recently released a follow up improvement to how edit data was displayed based on editor feedback. [77]
Add a Link
[edit]We released “add a link” to 35 more Wikipedias. [78] [79]
We have a few Wikipedias remaining:
- German and English Wikipedia will be contacted at the beginning of January 2024.
- There are a few small wikis that will not receive the task until they have enough articles for the algorithm to work properly.
Community Configuration
[edit]- We shared Community Configuration 2.0 plans with technical stakeholders. [80] 🖂
- Initial Community Configuration design ideas have been shared and discussed with community members.
- A basic Community Configuration 2.0 demo is released on ToolForge.
- Developers can find some initial proof of concept code shared on gitlab.
Mentorship
[edit]When a mentor marked themselves as "Away", they were not getting their name assigned to new accounts when they returned. This has been fixed. [81]
We improved the message received by newcomers when their mentor quits, to reduce confusion. [82]
We worked on ensuring that all mentees are assigned to an active mentor. This required reassigning mentees with no mentors to a new mentor. We paused this as the clean-up script confused some editors. We will resume it when the identified blockers are resolved. [83]
It is now possible to create an Abuse Filter to prevent one user from signing up as a mentor. [84]
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
18:04, 1 December 2023 (UTC)
Growth News, April 2024
[edit]The Growth team will now send quarterly reports to keep you in the loop. Growth team weekly updates are available on wiki (in English) if you want to know more about our day-to-day work.
If you want to receive more general updates about technical activity happening across the Wikimedia movement (including Growth work), we encourage you to subscribe to Tech News.
Community Configuration
[edit]Growth features are currently configurable at Special:EditGrowthConfig
. This quarter we are working on making Community Configuration accessible for other MediaWiki developers while also moving Growth feature configuration to the new CommunityConfiguration extension.
An early version of Community Configuration can be tested at Spanish Beta Wikipedia. We plan to release the new Community Configuration extension to pilot wikis (Arabic and Spanish Wikipedia) in early May, 2024. The first non-Growth team feature to utilize Community Configuration will be Automoderator.
In parallel with the development, the Growth team will propose Community Configuration usage guidelines, Community Configuration design guidelines, and provide technical documentation.
Experiment Results
[edit]Add a Image experiment analysis results
The Growth team conducted an experiment to assess the impact of the “Add an Image” structured task on the Newcomer Homepage's "Suggested Edits" module. This analysis finds that the Add an Image structured task leads to an increase in newcomer participation on the mobile web platform, particularly by making constructive (non-reverted) article edits:
- The likelihood that mobile web newcomers make their first article edit (+17.0% over baseline)
- The likelihood that they are retained as newcomers (+24.3% over baseline)
- The number of edits they make during their first two weeks on the wiki (+21.8% over baseline)
- A lower probability of the newcomers' edits will be reverted (-3.3% over baseline).
Personalized praise experiment results
This feature was developed for Mentors as part of the Growth team's Positive Reinforcement project. When A/B testing on Spanish Wikipedia, we found no significant impact on retention, but we found a significant positive impact on newcomer productivity. However, we concluded that the results weren’t positive enough to justify the time investment from Mentors. We plan to discuss this feature with our pilot wikis, and consider further improvements before scaling this feature further. Meanwhile, communities willing to test the feature can ask to have it deployed. (T361763)
English donors encouraged to try editing
As in previous years, donors were directed to a Thank you page after donation (example). However, this year we tested a new “Try editing Wikipedia,” call to action on the Thank You page. This call to action linked to a unique account creation page. From this account creation page we were able to track Registrations and Activation (editing for the first time). During the English banner campaign, the Donor Thank you page led to 4,398 new accounts, and 441 of those accounts went on to constructively edit within 24 hours. (T352900)
Future work
[edit]Annual Plan
The Growth team and the Editing team will work on the WE1.2 Key Result in the coming fiscal year. We will start initial discussions with communities soon to help finalize our plans. (T361657)
Newcomer Homepage Community Updates module
We plan to A/B test adding a new Community Configurable module to the Newcomer Homepage that will allow communities to highlight specific events, projects, campaigns, and initiatives. We are early in the planning phase of this project that will take place first at our pilot wikis and wikis volunteering. We welcome community feedback on initial designs and plans, in any language at our project talk page.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
18:55, 23 April 2024 (UTC)
Growth News, July 2024
[edit]Community Configuration
[edit]The Growth team released Community Configuration at all Wikipedias. You can access it at Special:CommunityConfiguration
.
This new special page replaces Special:EditGrowthConfig
. For now, all Growth features can be configured using Community Configuration. Configuration for AutoModerator (T365046) and other features will be available in the future.
You can help with translations. The interface translation is done at Translatewiki.net. You can also help translate the documentation.
If you attend Wikimania 2024, please join us for the session about Community configuration's future!
Current work
[edit]Newcomer Homepage Community Updates module
We will add a new Community Configurable module to the Newcomer Homepage that will allow communities to highlight specific events, projects, campaigns, and initiatives. We have released a simple version available to beta wikis. We will conduct an A/B test at our pilot wikis using the new Metrics Platform. We still welcome community feedback on initial designs and plans, in any language at our project talk page.
Future work
[edit]Increase constructive activation on mobile
As part of the Growth team 2024/2025 Annual Plan, the Growth team will explore various ways to increase the percentage of newcomers who successfully start editing.
Editing a Wikipedia page requires too much context and patience. It means many trial and error for newcomers to contribute, meaning a steeper learning curve and potential discouraging reverts. To support a new generation of volunteers, we will increase the number and availability of smaller, structured, and more task-specific editing workflows (E.g. Edit Check and Structured Tasks). The Growth team will primarily focus on Structured Tasks, while working closely with the Editing team to ensure our work integrates well with Edit Check.
Stay informed
[edit]Growth team weekly updates are available on wiki (in English) if you want to know more about our day-to-day work. If you want to receive more general updates about technical activity happening across the Wikimedia movement (including Growth work), we encourage you to subscribe to Tech News.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
15:08, 30 July 2024 (UTC)
Growth News, October 2024
[edit]Current work
[edit]Newcomer Homepage Community Updates module
We will add a new module to the Newcomer Homepage that will allow communities to highlight specific events, projects, campaigns, and initiatives. We have released a simple version on beta wikis and we will soon start an A/B test on our pilot wikis. This module will only display on the Newcomer Homepage if communities decide to utilize it, so learn how to configure the Community Updates module, or share your thoughts on the project's talk page.
Constructive activation experimentation
After showcasing early design ideas at Wikimania, we conducted user testing of design prototypes. We now aim to engage communities in further discussions and plan to run a targeted experiment, presenting a structured task within the reading view to logged-in new account holders with zero edits.
This Community Configuration extension was developed to help communities customize wiki features to meet their unique needs. The Growth team is now helping other Wikimedia Foundation teams make their products configurable:
- The Moderation Tools team now provides Community Configuration for Automoderator. (T365046)
- Certain Babel extension settings will be configurable soon. (T328171)
Future work
[edit]As part of the Growth team annual plan, we will continue to investigate ways to increase constructive activation on mobile, while also working with Data Products to move forward A/B testing functionality via the Metrics Platform.
Community events
[edit]- Growth team members presented Community Configuration: Shaping On-Wiki Functionality Together at Wikimania (slides). The session recording is available to watch on YouTube. This session provided an update on the Community Configuration project and introduced details about the upcoming features that communities will soon be able to configure. Representatives from the Moderator Tools, Editing, Web, and Campaigns teams shared their plans for utilizing Community Configuration in the future. Following these presentations, the WMF Growth team's Benoît Evellin and Martin Urbanec answered audience questions.
- Habib Mhenni gave a presentation of how mentorship works at WikiIndaba 2024. The recording is available.
Stay informed
[edit]Growth team weekly updates are available on wiki (in English) if you want to know more about our day-to-day work. If you want to receive more general updates about technical activity happening across the Wikimedia movement (including Growth work), we encourage you to subscribe to Tech News.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.