Reading/Web/Desktop Improvements/Updates/ko



: 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.

: Page title/tabs switch
We are deploying one of our latest updates. The page title will be displayed above the tabs such as, , , , or.

With this change, we are improving two things. First, we are making it clear that the items in the tabs are related to the the page that's being viewed. It's becoming apparent when we put the page title first. This change also makes switching languages easier. It moved the language button into an even more prominent position at the top of the page. Learn more on Phabricator.

We have been introducing this change in small steps. Since the last days of June, it's been available to all users opted into the Vector 2022 skin, and some early adopter wikis. During the week of July 4, the change will become visible on all the early adopter wikis.

In addition to that, our next office hours will be on July 26 instead of July 12. This will allow us to prepare the communication about making Vector 2022 the default across more wikis. We are also working on better language support for office hours in the future. More information on this coming soon!

: Table of Contents is available
We have deployed the new table of contents. It makes it easier to gain context of the contents of a page and navigate the page without needing to scroll to the top.

It is currently available to three groups of users. First, all who use Vector 2022 and are not on our pilot wikis. Second and third - 50% of logged-in users of Hebrew and Basque Wikipedias. Next week, we will be A/B testing the table of contents across the rest of our pilot wikis. We would like to check if there's a decrease in the need to scroll to the top of the page.

Before all that, we prepared a series of prototype tests with both readers and editors. To read more about how we worked on the feature based on feedback, please see the project page.

Now, we are working on the feature based on the feedback from users mentioned in the second paragraph. In particular:


 * ToC on narrower screens. We have increased the threshold for which the ToC currently hides to 1000px. (See T306904 for more context). This was to make it more comfortable to read on narrower screens. This is a temporary fix, though. The conversation about the best solution will continue in T306660. By the end of April/early May we hope to have clear next steps on our preference of the options presented there.
 * We are beginning the work on reducing the margins for screens between 1000px - 1200px. This will make the table of contents smaller and create more space for text. We will track this in T307004 and will probably have the implementation ready within a few days.



: 목차 개발
저희의 3번째 프로토타입 테스트는 제안된 목차의 압도적인 지지를 보았습니다. 이를 기반으로 저희 팀은 이 기능의 개발에 집중했습니다. 새 목차는 계속 한 자리에 있기 때문에 사용자는 언제든지 목차에 접근할 수 있게 됩니다. 문서의 문맥을 이해하기 더 쉽게 만들어주기도 합니다. 그뿐 아니라 최상단으로 끝까지 스크롤하 않아도 페이지의 여러 부분을 둘러보는 것이 가능해집니다. 저희는 4월 초에 저희 파일럿 위키에 새 목차를 적용할 것으로 예상합니다.



: 문서 도구 피드백
저희 팀은 문서 도구(이른바 일반 문서 도구)에 관한 작업을 시작하고 있습니다. 우리의 목표는 사이드바 안에서 개개의 항목의 목적을 구별하기 더 쉽게 만드는 것입니다. 저희는 현재 제안된 프로토타입의 피드백을 수집하고 있습니다. 여러분의 의견을 기대합니다! 프로토타입 테스트 페이지로 이동하여 폼을 채워 주십시오.



: 고정 헤더가 페이지 최상단으로 스크롤해야 하는 필요성을 줄여주는 것으로 확인
2022년 1월 5일부터 1월 31일까지 저희는 A/B 테스트를 수행했습니다. 저희는 고정 헤더 적용 시 미치는 영향도를 측정하기를 원했습니다. 이 테스트는 저희의 파일럿 위키들 중 22곳에서 수행되었습니다. 새로운 스킨 버전의 트리트먼트 그룹에 속한 로그인한 사용자들은 고정 헤더를 보았습니다. 컨트롤 그룹에 속한 사용자들은 오래된 기능을 보았습니다.

AB 테스트의 주된 목표는 저희의 가설을 시험하는 것이었습니다. 저희는 고정 헤더가 페이지의 최상단까지 스크롤할 필요성을 줄여줄 것이라고 예상했습니다. 전반적으로 저희는 (고정 헤더가 없는) 컨트롤 그룹 대비 (새 고정 헤더가 있는) 트리트먼트 그룹의 15개 파일럿 위키의 로그인한 사용자들에 의해 세션 당 평균 15%의 스크롤 감소를 보았습니다. 나머지 7개 파일럿 위키에서는 거의 활동이 없어서 해당 위키들은 제외했습니다. 결과는 저희의 가설이 옳았음을 입증했습니다. 페이지에 고정 헤더를 추가하여 페이지의 상단까지 스크롤할 필요성을 상당 부분 줄여주었습니다. 전체 보고서 읽기.



: 더 많은 파일럿 위키
데스크톱 개선은 12개 이상의 위키에서 기본값입니다. 해당 위키는 크게 다음과 같습니다: 모로코 아랍어/인도네이사어/태국어/베트남어 위키백과, 프랑스어 위키인용, 포르투갈어/폴란드어 위키뉴스, 베트남어 위키책, 미디어위키 위키. 이 위키들뿐 아니라 저희는 위키미디어 재단 관련 위키들에 변경을 적용했습니다: 위키미디어 재단 거버넌스 위키, 공동 협업 위키, 전략 위키. 현재 약 30개의 파일럿 위키가 있습니다. Among them, there are wikis of different scripts and sizes, written on all continents, and run both by the communities and the Foundation. 머지않아 적어도 하나의 위키문헌이 해당 목록에 추가되길 희망합니다.



: 고정 헤더 개발
저희 팀은 고정 헤더 개발을 작업하고 있습니다. 로그인한 사용자가 페이지를 통해 중요 기능(검색, 토론 문서, 역사 문서, 언어 전환 등)에 접근할 수 있게 합니다. 저희는 고정 헤더의 최초 버전 개발을 마쳤습니다. 이제 우리는 1월 말 파일럿 위키에 A/B 테스트를 적용할 예정입니다. 이 헤더는 프로토타입 테스트의 사용자 테스트 결과와 자발적 사용자들의 답변에 기반을 두었습니다.



: 언어 전환 기능
Earlier this year, we moved the language button to a more convenient location at the top of the page. However, the results of our A/B test indicated that the new location of the button might be difficult to discover in the following cases:


 * For users that are accustomed to the previous location of the language switching functionality
 * For users that tend to switch languages across multiple wikis. In the latter case, this created a situation where the language switching functionality was available in different locations depending on the wiki used and whether that wiki was a part of the pilot wikis.

To improve on these issues, we are changing the new language button. Our goal is to make it easier to find across all scenarios. We hope to release these improvements in January 2022.



: 목차 프로토타입 테스트
Over the next few months, our main focus will be on making the table of contents persistent. Currently, the table of contents is available only at the top of the page. It is difficult to gain context on an entire article or page, or to navigate to individual sections, when outside the top of the page. We hope to make the table of contents easier to navigate through a page, as well as to understand its context.

We will be publishing our research, further documentation, and mockups, over the next few weeks. In the meantime, we welcome you to give us feedback on our current prototype on this page.