Reading/Web/Desktop Improvements/ru

From MediaWiki.org
< Reading‎ | Web
Jump to navigation Jump to search
This page is a translated version of the page Reading/Web/Desktop Improvements and the translation is 21% complete.
shortcut: DIP
Other languages:
Deutsch • ‎English • ‎español • ‎français • ‎polski • ‎português • ‎čeština • ‎русский • ‎עברית • ‎বাংলা • ‎中文 • ‎日本語
Описание скриншота текущего темы Vector. Область содержание статьи (article content) не будет изменяться, будут улучшаться другие области.

Наш интерфейс для настольных компьютеров со временем менялся, но после появления темы Vector (используется на сайте по умолчанию) большинство этих изменений были сделаны добровольцами и доступны только в прототипах, пользовательских сценариях, гаджетах и пользовательских темах. Мы думаем, что пришло время внедрить некоторые из этих идей, чтобы они стали использоваться по умолчанию. В течение следующих нескольких лет команда будет изучать и разрабатывать улучшения для рабочего стола на основе исследований и существующих инструментов. Наши цели - сделать Wikimedia вики более привлекательными для новых читателей и редакторов, а также сделать его проще и чтобы как можно скорее его могли начать использовать (как новички, так и опытные редакторы).

Этот проект находится на самой ранней стадии обсуждения. Нет никакого конкретного плана. Нам нужна совместная работа и обратная связь по общим для всех проблемам, а также нам нужны ваши мысли относительно стартовых идей, приведенным ниже.

Как вы можете помочь

Обратная связь: Пожалуйста, ознакомьтесь с подробностями и подстраницами, а также поделитесь своими отзывами на странице обсуждения об идеях и макетах, которые мы собрали до сих пор — Как их можно усовершенствовать в дальнейшем? Какие важные соображения в настоящее время не зафиксированы в документах?

Исследования и идеи: отредактируйте разделы «Фаза 1: Дизайнерские идеи» ниже, чтобы добавить новые идеи, заметки, ссылки на прошедшие обсуждения, ссылки на существующие гаджеты/скрипты, ссылки на хорошие внешние дизайны, шаблоны для рассмотрения и т.д.

Individual testing: Once development begins, we will make the ongoing work available directly via a new skin option in Preferences. You will be able to individually opt-in and test the changes.

Whole wikis: We are also looking for any wikis that are interested in helping with widespread testing, such as changing the local default for logged-out site users. If you think your community might be interested, please ask us if you have any questions, then start a local discussion, and once there is local consensus add a link to that discussion on the talk page.

Longer comments and thoughts are welcome on the talkpage, in any language.

Обновления

Май 2020: Первое развертывание в officewiki и testwiki

This Monday we deployed the first visual change of the improved version of the desktop skin on our first production wikis - Officewiki (used internally by the WMF) and Testwiki (for general testing purposes). On these wikis, you will notice a reconfiguration of the project logo which is the first portion of our improved header. You can also turn the updated skin version on and off from the sidebar and your user preferences. In the next couple of weeks, we will also be deploying a collapsible sidebar for these wikis, followed by a deployment of these changes to our full set of test wikis.

We have also introduced a query string parameter using which you can see the state of the Vector skin on any wiki by adding the parameter ?useskinversion=2 to the url. Example: Paris on French Wikipedia

Subscribe to our Newsletter and check the previous updates.

Постановка проблемы

  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).
  2. Вики-движок от Викимедиа не прост в использовании
    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).
  3. Модель вики от Викимедиа не легка для понимания
    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:

New readers Not a welcoming experience — overwhelming, disorienting, unfamiliar, jarring, not trustworthy
Existing readers Not an ideal reading/learning environment — cluttered, lack of emphasis on content, lack of emphasis on popular actions, opaque, lack of emphasis on depth & breadth of knowledge
New editors Difficult to get started — intimidating, confusing, disorganized, exclusive
Existing editors Not an ideal editing/community environment - lack of emphasis on useful actions, disorganized tools, many tools given prominence are not helpful

Цели

Here are the outcomes we're working towards:

  • 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

Ограничения

Here is a list of things we would explicitly like to keep in mind:

  • 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

Сроки

We'd like to note that due to the effects of the current pandemic on our team and the WMF as a whole, the timeline below is tentative. We still plan on continuing with the same steps and in the same order, but it might take us a bit more time than initially intended. We will update the dates below regularly to reflect this.

Here is the roughly planned timeline, which will change based on progress:

  • Phase 1: May – September 2019: Investigation and research, figuring out where we can create value, finding focus
  • Phase 2: July – November 2019: Developing focus areas, sketching and prototyping ideas, starting conversations
  • Phase 3: October 2019 – January 2020: Continued user testing and design refinements
  • Phase 4: January 2020 - May 2020: Prototype feedback and iteration. Building out first features - new header and collapsible sidebar. Deploying header to Office Wiki and Test Wiki
  • Phase 5: May 2020 - July 2020: Prototype, user test, and ship header and collapsible sidebar features to test wikis as default. Deploy header and collapsible sidebar features to all wikis as an opt-in preference
  • Phase 6+: July 2020 - TBD: Continuing with feature sequence

Метрики

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)

Feature Sequence

This is a summarized overview of the features we are considering adding or iterating on throughout the course of the project. A more detailed list is available on a separate page - we encourage looking through that page for more information. As we go through with design, requirements gathering, and user testing for each feature, we will also publish a separate page per feature with more detail. These will be linked from the title of the feature.

  1. New Header
  2. Collapsible Sidebar
  3. Moving language links to the article title bar
  4. Sticky site and article headers
  5. User Menu
  6. Improved search
  7. Improved language switching
  8. Table of contents
  9. Article tools
  10. General aesthetic refinements

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:

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 2020)

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.

Этап 1: Дизайнерские идеи

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

Более доступные повседневные действия

  • Sticky header with search, table of contents, edit links
  • 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
  • Jump to the top of the page
  • Paragraph (¶) symbols on headings: visible only when hovering, next to the edit icon, to easily copy links to sections.

Логическая и полезная расстановка объектов

  • Consolidated user menu (e.g. collapsing things like "Log out", "Preferences", and "Beta", inside a dropdown menu)
  • Preferences for logged out users
  • Moving article actions from the sidebar to within the article
    • Examples: Winter, Timeless skin at 1085px or thinner, ...
  • Easily navigate through articles - load page content using JS in background without loading the whole page

Подстраницы