Reading/Web/Desktop Improvements/zh

我们的桌面界面随着时间的推移一直在变化，但是自Vector皮肤（默认网站设计）推出以来，这些变化中的大多数都是由志愿者主导的，仅在原型、用户脚本，小工具和志愿者领导的皮肤中可用. 我们认为是时候采纳其中一些想法并将它们带入默认体验了. 在接下来的几年中，网页阅读团队将基于研究和现有工具来研究和开发对桌面体验的改进. 我们的目标是使维基媒体更受新读者和编辑的欢迎，并使所有人（新手和资深编辑）都更容易、快捷地使用.

这个项目处于讨论的早期阶段. 尚无“具体计划或发展”. 我们需要您对问题的总体重点领域的协作和反馈，以及您对以下初始设计思想的看法.

您能如何提供帮助
研究与想法：请编辑下面的“第1阶段：设计想法”部分，以添加新的想法、记录、过去讨论的链接、现有小工具/脚本的链接，好的外部设计模式的链接等.

个人测试：开发开始后，我们将通过“参数设置”中的新外观选项直接使正在进行的工作可用. 您将可以单独选择加入并测试更改.

整体维基：我们也在寻找对帮助进行广泛测试感兴趣的任何Wiki，例如为登出站点用户更改本地默认值. 如果您认为您的社群可能感兴趣，有问题请尽管向我们提问，然后开始进行本地讨论，一旦达成本地共识，请在讨论页面上添加指向该讨论的链接.

欢迎在讨论页面上以任何语言发表更长的评论和想法.

2019年9月：Wikimania研究报告


在Wikimania 2019期间，我们采访了编辑者，目的是分享我们即将进行的桌面改进项目的计划，并收集有关许多初步设计思想的宝贵反馈. 我们的研究包括用户访谈、自由形式的实践反馈以及分组讨论的演示文稿，以便进行更集中的讨论. 我们已经就收到的反馈发布了一份英文报告 和PDF摘要（英文）. 总体而言，我们在选定的重点领域以及想法的各个原型方面收到了积极的反馈. 但是，我们也能够确定需要改进的地方.

在接下来的几周中，我们将反复查看这些反馈，并计划开发一个可以在维基上为更多受众测试的原型.

在下面的幻灯片中，我们测试了19个想法的样本. 有关更多背景信息，请阅读完整的报告，然后在讨论页面上给我们反馈！

September 2019: Desktop usage and behavior data analysis
As a part of our research process, we wanted to learn more about the way people currently use the site. In particular, how often they use available functionality such as links in the sidebar, language switching, and search. We have published our results. Overall, usage of sidebar links is low - only about 0.5% of all logged out users and 1.6% of all logged-in desktop users clicked on one of the pages linked in the sidebar. Language switching usage varied, generally based on the size of the wiki, with smaller wikis switching languages more often.

2019年8月：Wikimania上的研究和头脑风暴


Wikimania provided us with the opportunity to speak with experienced members of our communities. Over the five days of the conference we were able to share the plans for the project, and collect valuable feedback on a number of design ideas. Our research consisted of user interviews, a free-form feedback exercise, and a presentation + brainstorming session (you can see the slide-deck we used at the side). We will soon be publishing the summary of the feedback, as well as interview session results.

2019年8月：技术研究
To explore different technical possibilities for the project, the team spent a week hacking on different approaches to a single problem - how to enable the sidebar in the desktop experience to be collapsible. We are hoping to use the results from these experiments to determine the technical architecture for the improvements, as well as the skin we would like to build these improvements within. Here is a list of the experiments themselves:


 * Building a collapsible sidebar using a fork of the vector skin
 * Building the desktop sidebar within the Minerva skin. An exploration in the question: "is there a world where we have the same skin for desktop and mobile?"
 * Building a collapsible sidebar using user styles only

问题陈述

 * 1) 维基媒体计划不受欢迎
 * Wikimedia wikis’s desktop sites are not a welcoming or familiar experience for new readers. It does not match the expectations created by the modern web and our other platforms (the Android and iOS apps as well as the mobile website).  It feels disorienting and disconnected due to the haphazardly organized navigation and interface links. In turn, this causes readers and editors to have less trust in Wikimedia wikis, to be less likely to explore Wikimedia wikis, and eventually, to use our sites less than they otherwise would (i.e. a decrease in retention).
 * 1) 维基媒体不易于使用
 * Readers (new readers especially) are unable to intuitively perform basic functions like switching languages, searching for content, or adjusting reading settings. Additionally there is a lot of clutter that distracts from the content they are interested in. New editors are faced with a similar barrier; an interface that is not welcoming or intuitive and is cluttered.  It is difficult for them to perform basic tasks necessary for contribution, such as setting up an account, opening the editor, or learning how to use special pages for moderation purposes (e.g. history pages to find&revert vandalism). All users can have problems with the sites not being properly "responsive", which leads to issues like really wide content or really narrow content (depending on screen and window sizes). By keeping the status quo, we are preventing people who are eager to contribute from being able to do so (i.e. experience bias).
 * 1) Wikimedia wikis’s model is not easy to understand
 * Currently, a very small percentage of readers understand how Wikimedia wikis function. Our interfaces do not highlight the inner workings of the site in an intuitive way. Many readers are not aware that the content they are reading is written by volunteers and updated frequently, or that they can potentially contribute as well.

In addition, the large difference in experiences among our various products (desktop, apps, and the mobile web), makes it difficult for readers to know the connections between our products and to associate them with the content itself. This creates a lack of unity in the concept of Wikimedia sites.

Summary by audience:

目标
以下是我们正在努力取得的成果：


 * Make it easier for readers to focus on the content
 * Provide easier access to everyday actions (e.g. search, language switching, editing)
 * Put things in logical and useful places
 * Increase consistency in the interface with other platforms - mobile web and the apps
 * Eliminate clutter
 * Plan for future growth

局限性
这是我们明确要记住的事情列表：


 * Not touching the content - no work will be done in terms of styling templates or to the structure of page contents themselves
 * Not removing any functionality - things might move around, but all navigational items and other functionality currently available by default will remain
 * No drastic changes to the layout - we're taking an evolutionary approach to the changes and want the site to continue feeling familiar to readers and editors

在Wikimania 2019期间，我们采访了编辑者，目的是分享我们即将进行的桌面改进项目的计划，并收集有关许多初步设计思想的宝贵反馈. 我们的研究包括用户访谈、自由形式的实践反馈以及分组讨论的演示文稿，以便进行更集中的讨论. 我们已经就收到的反馈发布了一份英文报告 和PDF摘要（英文）. 总体而言，我们在选定的重点领域以及想法的各个原型方面收到了积极的反馈. 但是，我们也能够确定需要改进的地方.

以下是大致计划的时间表，该时间表会根据进度而变化：


 * 阶段1：2019年5月至2019年9月：调查和研究，找出我们可以创造价值的地方，寻找重点
 * 阶段2：2019年7月至2019年11月：开发重点领域，草绘和制作原型想法，开始对话
 * 阶段3：2019年10月至2020年1月：持续的用户测试和设计改进
 * 阶段4+：待定

量表
Below is a draft of the core metrics we want to measure through the course of the project. As we define the changes we want to make with more specificity, we will expand and iterate on this list.

Increase utility among our existing audiences, proxied by:


 * Interactions
 * Increase searches per session by 5% over the course of the project
 * Increase language switching per project by 5% over the course of the project
 * Affinity
 * Increase in positive and welcoming sentiments towards the site (via surveys and user testing)
 * Increase in sentiments of trust and credibility (measured via surveys and user testing)

Research and design process
General note: our process is not particularly strict. It is based loosely on research and design process best practices, however it is also relatively emergent and flexible, in that we are engaging in ad hoc activities and explorations as they feel appropriate. While we've outlined the research and design process in three phases below, in practice the phases overlap. Additionally, for the time being there doesn't seem to be a clear way of separating research activities from design activities (they are interrelated) so we're discussing them together.

Phase 1. Investigation and research, figuring out where we can create value, finding focus (May 2019 – September 2019)

 * Main page: /Research and design: Phase 1

We began by considering the current default experience on desktop (Vector) and asking ourselves: in what ways can we improve upon this? Where are opportunities to modify the interface in order to create a better experience for all readers and editors? How can we make it easier for people to do the things they want to do? How can we create a more pleasing reading environment? Of course while exploring these questions we kept in mind the project's constraints. The research and design activities we engaged in in order to explore these questions included:


 * Understanding the history of the desktop interface
 * Reading previous Wikipedia research conducted by the Wikimedia Foundation or other research institutions and individuals
 * Discussions at our team offsite to develop a shared understanding of the project and generate ideas
 * Winter, Timeless, and other Wikipedia redesigns
 * Reading about redesigns/updates of other large websites (Reddit, Twitter, etc.)
 * Conducting an audit of other large websites to try and glean common structural elements

The output from phase 1 was: a better understanding of the desktop interface, and proposed focus areas for improvements. We didn't have strict criteria for what a focus area could be. Generally speaking it was an idea of an improvement we could make, though at varying levels of specificity, such as: a less cluttered reading experience, or language switching ease. The proposed focus areas are:


 * Creating a more focused and "quiet" reading environment by consolidating or optionally collapsing navigational links, including:
 * Main sidebar navigation
 * Article tools
 * User tools
 * Language switching
 * Search
 * Article navigation / table of contents

Additional, more feature-specific, ideas that came up: reading preferences (e.g. dark mode), share button, larger edit button / add new article button (for smaller wikis) / making it more obvious how to "get involved", article stats / activity summary.

Phase 2. Developing focus areas, sketching and prototyping ideas, starting conversations (July 2019 – November 2019)

 * Main page: /Research and design: Phase 2

The research activities and conversations in phase 1 helped us develop a better understanding of the landscape we were working within (i.e. the desktop interface). It also helped us develop potential focus areas to further investigate (while still remaining open to new ideas). Our next goal was to dig a bit deeper into the focus areas through sketching, prototype, and most importantly conversations with the community. The research and design activities included:


 * Understanding past work, research, and experiments in respective focus areas
 * Obtaining general usage data about the respective focus areas
 * Sketching out and prototyping early ideas to help facilitate conversations
 * Forming early hypotheses
 * User interviews and other feedback at Wikimania
 * Community feedback via MediaWiki (happening soon)
 * User interviews with newcomers and casual readers (happening soon)
 * User testing on usertesting.com (happening soon)

The output from phase 2 will include: reactions to sketches of specific interface improvements within the focus areas, a refined (i.e. more opinionated and informed) sense of which improvements are worth pursuing, a proposal for the sequence in which we could implement proposed improvements.

Phase 3. Continued user testing and design refinements (October 2019 – January 2019)
Phase 3 will be a cycle of: further testing the specific ideas that came out of phase 2, then refining our designs in response to what we learn. There are potentially some things that need to be tested as betas on actual wikis. We will be working to identify these things and figure out how we plan to test them in beta (i.e. what data we would be tracking, and what decisions we'd be making based on what behavior we see).

The output of phase 3 will include: nearly finalized designs (though we usually leave room for additional iterations during implementation) and a plan for what we want to learn as we roll things out in beta, and what decisions/changes we would make based on that information.

Phase 1: Design ideas
A few of the many ideas that have been suggested are below. Please add any prominent ideas and links you know of:


 * NOTE for editors: Please edit the English version to add ideas and links, or comment on the talkpage. Don't worry about the "tvar" markup if you don't know it. We will add it in afterwards.

Focusing on the content, distinguish content from user-interface Easier access to everyday actions Putting things in logical and useful places
 * Collapsible sections in sidebar
 * Examples: Hebrew Wikipedia, ...
 * Research: Usability initiative research on collapsible languages links, Usability initiative mockups on collapsible sections within the sidebar
 * Collapsible sidebar
 * Examples: Wide Skin (enwiki script), Hide Vector sidebar (enwiki script), Timeless skin sidebar (responsive-layout), ...
 * Floating sidebar
 * Examples: FloatSide (enwiki script), ...
 * Sticky header with search, table of contents, edit links
 * Examples: FloatHead (enwiki script), FloatHead (another enwiki script), Floater (enwiki script), Winter (historical prototype), Timeless (alternative skin), ...
 * Research: Usability-wiki
 * More prominent language switching (moving the language switcher to the top of the page)
 * Examples: Timeless skin at 1325px or wider and at 1085px or thinner, ...
 * Sticky table-headers
 * Examples: Gadget-StickyTableHeaders (enwiki gadget)
 * Consolidated user menu (e.g. collapsing things like "Log out", "Preferences", and "Beta", inside a dropdown menu)
 * Examples: Compact personal bar
 * Preferences for logged out users
 * Examples: Accessibility settings/preferences (T91201), ...
 * Moving article actions from the sidebar to within the article
 * Examples: Winter, Timeless skin at 1085px or thinner, ...