The Signpost

Technology report

Vector (2022) deployment discussions happening now

Contribute  —  
Share this
By EpicPupper, SGrabarczuk, and GPT-3
All sections of this report, except for "English Wikipedia community discussing the deployment of the Vector (2022) skin", were written with the assistance of GPT-3, OpenAI’s large-scale language-generation model. More information on Signpost GPT-3 articles can be found here. Upon generating draft language, the author reviewed the text and takes ultimate responsibility for the content of this publication.

English Wikipedia community discussing the deployment of the Vector (2022) skin

The slides to the latest Wikimania presentation about Vector 2022

Since July, a discussion about the switch to the Vector 2022 skin on English Wikipedia has been taking place. The discussion is focused on identifying what changes need to be made to the skin prior to launching the conversation around deployment.

The Wikimedia Foundation Web team is finalizing the changes that will be needed, and preparing a Request for Comment process around the deployment. The process is expected to start in early September. If you are an English Wikipedian who has feedback or questions around the new skin, the Web team encourages you to check out the new FAQ and add your thoughts to the current conversation.

About the skin

Vector (2022) is focused on making the interface more welcoming and comfortable for readers and useful for advanced users, especially those from diverse backgrounds and geographies. The skin builds upon the current default Vector legacy (2010) skin to introduce a series of feature changes. The results of quantitative (A/B and multivariate) testing and qualitative (user research and prototype) testing show that these changes make it easier to read and learn, navigate within the page, search, switch between languages, user page and user tools, and more, without negative effects to pageviews, account creation, or edit rates.

The skin has been in development for the past three years and has gone through rigorous testing. Currently, it is the default on half of the top 20 wikis, including Japanese, French, and Portuguese Wikipedias, in addition to many other projects. The team’s current focus is on bringing it as the default across all wikis.

Throughout the process, the team has been writing about their experience and motivations for building the skin on the Diff blog. Most recently, they published an in-depth blog post that focused on equitable product development and ways in which the voices of the current communities and readers globally were central to the development of the new skin. The post is available in 7 languages.

The results from Vector (2022) at a glance
  • The sticky header makes it easier to access tools that editors use often. It decreases scrolling to the top of the page by 16%
  • The new table of contents makes it easier to navigate to different sections. Readers and editors jumped between sections 50% more than with the old table of contents
  • The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on
  • The collapsible sidebar allows readers and editors to choose whether they want to see the main menu or not. Testing shows that this allows people to better focus on their current task - reading with a collapsed menu, or editing with an open menu
  • The language switching menu makes it possible to switch languages without scrolling
  • The user menu collects all user links in a single place, making it easier to understand what each link does. In testing, 71% of surveyed editors reported positive experiences with the new menu

OV (WMF), SG (WMF)

Private Incident Reporting System

On Italian Wikipedia, there's a 3-step policy in place for conflict resolution. This map visualizes this process and tries to identify opportunities for automation for both editors and admins.

The Wikimedia Foundation is building a "Private Incident Reporting System" (PIRS) to make it easy for users to report harmful incidents safely and privately. The newly-formed Trust and Safety Tools team has been tasked with building the PIRS. The team is studying previous research and community consultations to inform their work. They are also mapping out conflict resolution flows across wikis to understand how communities are currently managing conflicts. The goal of the project is to make it easier to address harassment and harmful incidents, ensure the privacy and safety of those reporting, as well as ensure the report reaches the correct entity that needs to process it. In Phase 1 of the project, the team wants to put out some rough ideas around possible product direction, consult with the community on mockups and ideas, and gather feedback from users. They also want to identify wikis that they can pilot PIRS on, establish a baseline for what they’re going to do in Phase 2, and identify potentially helpful metrics to look at when they start building. In Phase 2 of the project, the team wants to start building software based on Phase 1 findings and feedback. You are invited to provide feedback and answer questions about your experiences with inappropriate behavior on Meta. E

In brief

New user scripts to customise your Wikipedia experience

Bot tasks

Recently approved tasks
Current requests for approval

Latest tech news

Latest tech news from the Wikimedia technical community: 2022 #33, #34, & #35. Please tell other users about these changes. Not all changes will affect you. Translations are available on Meta.

Installation code

  1. ^ Copy the following code, edit your user JavaScript, then paste:
    {{subst:lusc|1=User:Novem Linguae/Scripts/ReviewStatus.js}}
S
In this issue
+ Add a comment

Discuss this story

The results of quantitative (A/B and multivariate) testing and qualitative (user research and prototype) testing show that these changes make it easier to read and learn, navigate within the page, search, switch between languages, user page and user tools, and more, without negative effects to pageviews, account creation, or edit rates.
This has been extensively discussed at the Village Pump, and I remain unconvinced that the WMF is testing for the right things to actually show this. For example, with the sticky header, they only test that the sticky header is used, rather than testing whether it makes it easier to navigate within the page. BilledMammal (talk) 01:00, 1 September 2022 (UTC)[reply]





       

The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0