Reading/Web/Desktop Improvements/ru

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

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

В настоящее время на большинстве вики только авторизованные пользователи могут включить изменения индивидуально. На выбранных вики наши изменения применяются ко всем по умолчанию, и зарегистрированные пользователи могут отказаться от них. Мы надеемся постепенно увеличивать набор вики-сайтов «раннего внедрения», пока наши улучшения не станут стандартными для всех вики в июле 2022 года.

Before, the interface…
''' …did't match the expectations. …was cluttered and not intuitive. …did't highlight the community side. …wasn't consistent with the mobile version. '''


 * 1) The desktop interface did not match the expectations created by the modern web platforms. It felt disorienting and disconnected. Navigation and interface links were organized haphazardly.
 * 2) There was clutter that distracted users from focusing on what they came for. It was challenging for readers to focus on the content. It was not possible for them to intuitively switch languages, search for content, or adjust reading settings. New editors were unable to use their intuition to set up their account, open the editor, or learn how to use non-article pages for moderation purposes.
 * 3) A very small percentage of readers understood how Wikimedia wikis functioned. Many readers were not aware that the content they were reading was written by volunteers and updated frequently, or that they could potentially contribute as well.
 * 4) The large difference in experiences among our desktop interface, apps, and the mobile web, made it difficult for readers to connect our products. There was a lack of unity in the concept of Wikimedia sites.

Principles
''' We do not touch the content. We do not remove any functionality. We do not change skins other than Vector. We are inspired by the existing gadgets. We do not make major changes in single steps. '''


 * 1) We work on the interface only. No work is done in terms of styling templates, the structure of page contents, map support, or cross-wiki templates.
 * 2) Skins other than Vector are out of the scope of our adjustments. We have frozen Vector to Legacy Vector, and begun deploying our features as parts of the new default Vector.
 * 3) Though our changes are easily noticeable, we have taken an evolutionary approach and wanted the site to continue feeling familiar to readers and editors. Each feature has been discussed, developed, and deployed separately.
 * 4) We have tested our improvements in collaboration with a diverse set of volunteering early adopter wikis, both Wikipedias and sister projects.
 * 5) Both prior to development and after deployment, we collected data (via A/B testing, prototype feedback rounds, etc.). In the case of significantly negative results, we committed to rolling back our changes.
 * 6) We have analysed many wikis and have noticed many useful gadgets. Some of them definitely deserved to be surfaced and be a part of default experience.
 * 7) Elements of the interface have moved around, but all navigational items and other functionality available previously by default have remained.

Deployment plan and timeline
The skin is now ready to become the default on any wiki.

The timeline

Get involved & Contact

 * Test individually: in Preferences, check the option . You can also enable our changes using the Global preferences.
 * Test individually: in Preferences, check the option . You can also enable our changes using the Global preferences.


 * Promote: Inform your community. Share our updates and blog posts.
 * Report bugs: to report a bug, create a task in Phabricator and add project.


 * Translate: help us translate related pages:

What features have been added
Each feature was built and implemented separately, over time. Our decisions were based on community feedback, user testing, and extracted API data.