Reading/Web/Desktop Improvements/Updates/zh



: Continuing work on Vector 2022, and making plans for the new fiscal year
We have been focusing on continuing deployments across remaining wikis and running experiments for further improvements. We have also done some work on the plans for future projects.


 * Rollouts. Vector 2022 is now the default skin on Polish and Spanish Wikipedias, and French Wikinews. We are also discussing with the Chinese Wikipedia community. Special gratitude to everyone who helps us and editors have better understanding in the discussions, find and resolve bugs, and explain decisions. If the community of your wiki would like our skin to become the default, please reach out to us!
 * Experiment: toggle indicator. We have launched an experiment which introduces an indicator pointing to the fixed width toggle. This is to ensure that readers are aware of the location of the toggle and able to switch between full and fixed width. (T335307)
 * Vector 2022 Zebra9 prototype with framed menus logged-in.png Content separation (Zebra #9) A/B test. We will run an experiment that compares different content separation layouts for the interface (based on this prototype). The experiment will be run in May across a set of 10 large to medium-sized Wikipedias. Once the experiment is complete, we will analyze the data and continue the process of selecting the best page layout. Read more about the on-wiki test here. For more information, check our documentation on the previous user testing experiment. Many thanks to everyone who has commented on this topic on our project talk page, on other wikis, or at online meetings with us! (T333180, T335972)
 * Plans for the future. In the next fiscal year of the Foundation, we'll be working on new projects. We invite you to read the draft of the Wikimedia Foundation annual plan, section Infrastructure, Bucket: Wiki Experiences. Also, read the more detailed description "WE2: Reading and media experience". This is the part our team will focus on. Among others, dark mode and reading lists are mentioned as examples of the possible projects. We will be glad to read your comments on the talk pages of the linked Meta-Wiki pages. Post in any language! The deadline is.
 * For more information about dark mode, see the Community Tech's team update where they have handed this most popular Wishlist proposal over to us. In the update, they have also shared some details on how we would be working on this project.



: Vector 2022 on more wikis and other updates
Over the past few months, the team has been preparing and changing the skin on the largest Wikipedias. Vector 2022 has become the default for all logged-in and logged-out users on Czech and English Wikipedias.

Since then, we have been discussing further improvements to the skin with the communities. As a result of these discussions as well as working on the previous plans, we've implemented many changes. These include:


 * Screenshot of the Vector-2022 skin's fullscreen toggle.png Persistence and availability of the full width toggle.  The full width toggle (available at the bottom of the page) is now persistent for both logged-out and logged-in users. This means that they see the width of their choice in spite of refreshing the page or opening a new one. The toggle is also available at narrower screen widths.
 * Moving article tools.jpg New page tools menu. 
 * It allows for a separation between navigation related to the entire wiki and tools related to a specific page. In the first group there are, for example, Main page and Random page. In the second group there are, for example, What links here, Related changes, and Cite this page. The new menu also collects the page-specific tools in a single menu. Before, some of these links were the main menu (sidebar) or in the More menu (next to History). Our goal is to make it easier for new readers and editors to understand what these links do. Users also may pin and unpin the new menu. More information is available on the project page.
 * Making this change also has the benefit of showing the table of contents further up the page. Now, people need to scroll down to see the table of contents more rarely. This is one of the concerns we've been hearing over the last couple of days and hope this addresses it.
 *  Moving the log-in link outside of the drop-down menu for logged-out users.  This change makes it quicker to reach the log-in link, without requiring logged-out users to open the drop-down menu.
 *  Various small improvements to the Table of Contents (ToC) :
 * Increase the height of the ToC. This will allow the ToC to appear longer, and for more sections to be visible (T319315).
 * Where the page lands when clicking on a ToC link (T314419). We've heard that the ToC opens too close to the beginning of a section, without giving any space for the title and previous section. This change will increase this space, making it more comfortable when navigating.
 * Threshold for when a section is considered active, and marked in the ToC (T317661). We have also heard that a section is considered active only after the user has scrolled the previous section out of view. This had lead to some confusion on the active state. This change will allow sections to be shown as active earlier, when the majority of the section is displayed on the screen.
 * Navigating directly to sub-sections and expand the parent section if collapsed (T325086). Some of the feedback relates to the way that subsections appear on the page. We've heard that subsections should appear more consistently when needed. This change ensures that subsections are open when the user opens a direct link to that subsection.

 Upcoming changes and explorations  We are currently working on the following changes: It will be especially useful on pages like the Village Pump or coordination pages in the Wikipedia namespace (T317818).
 *  Page layout.  We wanted to address one of the main concerns which has come out of the feedback around the skin so far. It's about the separation of content, and the brightness of the interface. We've developed a prototype we would like to get your feedback on. How should we measure the potential changes as compared to the current layout? We've posted more details and specific questions on the talk page. There are a few sections for discussions in different languages. Add your comments and questions there!
 *  Configuration of the table of contents.  We want to allow the ToC to be more configurable. Then, editors could determine when the ToC needs to be expanded or collapsed by default, and how many sections of the ToC can be shown by default. This will replicate the functionality of some of the "magic words" used in the ToC.

: More deployments, full width toggle, page tools, and other updates
For the past few months, our focus has been on discussing deployments across various large wikis. This includes English Wikipedia. Its community has agreed to have Vector 2022 as the default under some conditions. We have addressed those. Currently, we are discussing next steps with the English Wikipedia community.

We have also been switching the skin on in the majority of Wikipedias. Currently, there are ~300 Wikipedias with the default of Vector 2022. Last week, the skin became the default on Arabic and Greek Wikipedias. We hope to get to all the Wikipedias by the end of February 2023.

As a result of the feedback we've received, we've made more changes to the skin itself:

Limited width Page tools Accessibility
 * We have built a preference for logged-in users which allows for the width to be set across pageviews and wikis. The preference is available in the appearance section of the preferences page (""). It may also be set as a global preference.
 * We have built a toggle for logged-in and logged-out users. The toggle is available on every page if the monitor is 1600 pixels or wider. Selecting the toggle increases the width of the page.
 * Moving the page tools to the right side of the page. This change is about grouping the page tools, and creating separation from the wiki-wide tools. This change also addresses the concern for the location of the table of contents. It makes the sidebar (left menu) shorter and thus shifts the table of contents further up in the page.
 * We hope to make the updated tools menu available by the end of December, 2022. If you want to follow the development by previewing how the feature works, add  to the URL (if you're using Vector 2022 already) or   (if you're not using Vector 2022).

We have completed our review of the accessibility of the new skin with the American Foundation for the Blind (AFB). No major concerns were found. We are tracking the suggestions for further improvements. We are also addressing potential future improvements. The details are documented in T323634.

Sticky header We have added an edit button to the sticky header to make access to editing the full page easier (without requiring scrolling to the top of the page). After testing across a number of wikis, we concluded the following:
 * People were more likely to complete the edits they start using the sticky header in comparison to the edits initiated using other edit buttons on the page.
 * The edits people started by clicking the edit button in the sticky header, and ultimately published, were reverted less often than those initiated using other edit buttons on the page.

: Plans and conversations about the deployment across the Wikimedia wikis

 *  High usage on the early adopter wikis.  According to the recent study by the Product Analytics team, 87% of contributors active on the early adopter wikis use Vector 2022. Here, active contributors mean users who made at least 5 edits between 1 November 2021 and 31 August 2022. Thank you!
 *  Visual refinements.  We have completed the list of visual refinements. We planned to complete these before the deployments across more wikis. These changes included work on link colors, icons, and overall look and feel of Vector 2022. We welcome feedback and questions on any of these changes. Write to us on the project talk page.
 *  Decision of the English Wikipedia community through the Request for Comment.  For the past two months, we have been discussing with the English Wikipedia community. English Wikipedians have identified issues blocking the deployment of Vector 2022 on their home wiki. They have also requested that the decision on the deployment be made through the Request for Comment process. Our draft is now available. We're planning to launch the RfC on Wednesday, September 21. If you edit English Wikipedia, we encourage you to take part!
 *  Deployment plans across other projects.  We are planning deployment conversations across all of the other Wikimedia projects. We will first begin with the smallest wikis. By the smallest, we mean smaller than top 30 largest active communities. We hope to complete this during the first week of October, 2022. Then, we will begin conversations on medium to large-size wikis. Dates will depend on the consensus across individual communities.
 *  More community-facing activities 
 * We have posted a new essay on the Diff blog. It has a title Prioritizing equity within Wikipedia's new desktop. The essay is about why and how different groups of users were represented throughout the process of building Vector 2022.
 * We have published the expanded Frequently asked questions page. Take a look and tell us if it's useful. Soon, we will make it possible to translate it.
 * We also display banners encouraging to try out Vector 2022. The banners are only visible for logged-in users having Vector legacy (2010), the current default skin.

: Wikimania, visual refinements, and more changes
Having the structural changes to the features done, we are finishing development of Vector 2022. In particular:


 * We are working on the visual refinements. We will be changing the styles, link colors, font size, content area width, and more. This is based on the results of the feedback we received from our last round of prototype testing.
 * We are releasing updates to the table of contents (ToC) based on the feedback we've received from communities. These updates will make the ToC easier to use on smaller and larger screens. There will be more customization than before. Over the next few weeks, you will see the following changes:
 * The table of contents will be collapsible at all screen sizes
 * Once collapsed, the ToC will be available at the top of the page, next to the article title, as well as in the sticky header
 * The Editing team, whose focus is currently on improving talk pages, has added an "add topic" button to the sticky header on talk pages. This will make it easier to start a new topic on a talk page from any part of the page, without having to scroll to the very top. See their project page for more information on this change and the project overall.

We have also continued discussions on how to make Vector 2022 the default for more communities. Your feedback is helping us make the skin better. We appreciate that. Let's meet again! On Saturday August 13, we are having a session at Wikimania, and a separate meeting for questions and answers right after that.



：页面标题/标签切换
我们正在部署我们的最新更新之一. 页面标题将显示在选项卡上方，例如、、、或.

通过这一变化，我们正在改进两件事. 首先，我们要明确标签中的项目与正在查看的页面相关. 当我们将页面标题放在首位时，这一点变得很明显. 此更改还使切换语言更容易. 它将语言按钮移到页面顶部更显眼的位置. 了解有关Phabricator的更多信息.

我们一直在逐步引入这种变化. 自6月的最后几天以来，所有选择加入Vector 2022皮肤的用户和一些早期采用者wiki都可以使用它. 在7月4日这一周，所有早期采用者wiki上都将显示更改.

除此之外，我们的下一个办公时间将是7月26日而不是7月12日. 这将使我们能够准备有关使Vector 2022成为更多wiki的默认设置的沟通. 我们还在努力为未来的办公时间提供更好的语言支持. 更多信息即将推出！



：提供目录
我们已经部署了新的目录. 它使获取页面内容的上下文和导航页面变得更容易，而无需滚动到顶部.

它目前可供三组用户使用. 首先，所有使用Vector 2022并且不在我们的试点维基上的人. 第二和第三 - 50%的希伯来语和巴斯克语维基百科的登录用户. 下周，我们将对其余试点wiki的目录进行A/B测试. 我们想检查滚动到页面顶部的需求是否减少.

在此之前，我们为读者和编辑准备了一系列原型测试. 要了解更多关于我们如何根据反馈开发该功能的信息，请参阅项目页面.

现在，我们正在根据第二段中提到的用户反馈开发该功能. 尤其是：


 * 较窄屏幕上的ToC. 我们已将ToC当前隐藏的阈值提高到1000像素.  （有关更多上下文，请参阅T306904）.  这是为了让在更窄的屏幕上阅读更舒适.  不过，这是一个临时修复.  关于最佳解决方案的讨论将在T306660中继续.  到4月底/5月初，我们希望就我们对那里提出的选项的偏好有明确的下一步措施.
 * 我们开始着手减少1000像素到1200像素之间的屏幕边距. 这将使目录更小，并为文本创造更多空间.  我们将在T307004中跟踪这一点，并且可能会在几天内准备好实施.



：开发目录
我们的第三次原型测试的结果显示了对拟议目录的压倒性支持. 基于此，团队专注于开发此功能. 新的目录将是持久的——用户可以随时访问它. 它还将使您更容易理解页面的上下文. 除此之外，还可以导航到页面的不同部分，而无需一直滚动到顶部. 我们预计在4月上半月将新目录部署到我们的试点wiki.



：页面工具反馈
该团队正在开始研究页面工具（有时称为文章工具）. 我们的目标是更容易区分侧边栏中各个项目的用途. 我们目前正在收集有关我们提议的原型的反馈. 我们期待着听到您的想法！ 请访问我们的原型测试页面并填写表格.



：粘性标题确认减少滚动到页面顶部的需要
从2022年1月5日到1月31日，我们进行了A/B 测试. 我们想评估部署粘性标头的影响. 该测试在我们的22个试点wiki上运行. 被分配到具有新皮肤版本的治疗组的登录用户看到了粘性标题. 对照组中的用户看到了旧功能.

AB检验的主要目的是检验我们的假设. 我们一直期望粘性标题会减少滚动到页面顶部的需要. 总体而言，与对照组（没有粘性标题）相比，我们看到治疗组（使用新的粘性标题）的15个试点wiki上的登录用户每次会话的滚动量平均减少了15%. 在剩下的7个试点wiki上，活动太少，我们将它们排除在外. 结果表明我们的假设是正确的. 将粘性标题添加到页面显着减少了滚动到页面顶部的需要. 阅读完整报告.



：更多试点维基
桌面改进是另外12个wiki的默认设置. 最重要的是：摩洛哥阿拉伯语、印度尼西亚语、泰语和越南语维基百科、法语维基语录、葡萄牙语和波兰语维基新闻、越南语维基教科书和MediaWiki. 除此之外，我们还启用了维基媒体基金会相关维基的更改：维基媒体基金会治理维基、协作维基和战略维基. 目前，有近30个试点wiki. 其中，有不同文字和大小的维基，写在各大洲，由社区和基金会共同运行. 我们希望很快，至少有一个维基文库将被添加到该列表中.



：粘性标题开发
该团队一直致力于构建粘性标题. 它将允许登录用户访问整个页面的重要功能（搜索、讨论页、历史记录页、语言切换等）. 我们已经完成了第一版粘性标题的开发. 现在，我们预计在1月底之前将A/B测试部署到试点维基. 标题基于我们用户测试的结果和志愿者对原型测试的回答.



：语言切换迭代
今年早些时候，我们将语言按钮移到了页面顶部更方便的位置. 但是，我们的A/B测试结果表明，在以下情况下可能难以发现按钮的新位置：


 * 对于习惯了语言切换功能的先前位置的用户
 * 适用于倾向于在多个wiki之间切换语言的用户. 在后一种情况下，这会造成语言切换功能在不同位置可用的情况，具体取决于所使用的wiki以及该wiki是否是试点wiki的一部分.

为了改善这些问题，我们正在更改新的语言按钮. 我们的目标是在所有场景中更容易找到. 我们希望在2022年1月发布这些改进.



：目录的原型测试
在接下来的几个月中，我们的主要重点将是使目录持久化. 目前，目录仅在页面顶部可用. 当超出页面顶部时，很难获得整篇文章或页面的上下文，或者导航到各个部分. 我们希望使目录更容易在页面中导航，以及理解其上下文.

我们将在接下来的几周内发布我们的研究、进一步的文档和模型. 同时，我们欢迎您在此页面上向我们提供有关我们当前原型的反馈.