User:SGrabarczuk (WMF)/sandbox/2

Imagine a wardrobe
Over the last 10 years, there were many minor changes to the interface. Some of these were deployed by the WMF, and some were deployed locally (as gadgets developed by the communities). Most of these were not coordinated visually. This lack of constant coordination is normal. But when the entire picture is no longer clear at first glance, it is time for readjustments. This is how we perceive our project.

We would like to stepwise rearrange…

Currently, the interface…
'''…doesn't match the expectations. …is cluttered and not intuitive. …doesn't highlight the community side. …doesn't resemble the mobile version.'''


 * 1) The desktop interface does not match the expectations created by the modern web platforms. It feels disorienting and disconnected. Navigation and interface links are organized haphazardly.
 * 2) There is clutter that distracts readers and editors from focusing on what they came for. It is not possible for readers to intuitively perform basic functions like switching languages, searching for content, or adjusting reading settings. Similarly, new editors are unable to use their intuition to set up their account, open the editor, or learn how to use special pages for moderation purposes.
 * 3) A very small percentage of readers understand how Wikimedia wikis function. 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.
 * 4) The large difference in experiences among our desktop interface, apps, and the mobile web, makes it difficult for readers to connect our products. There is a lack of unity in the concept of Wikimedia sites.

Our goals
We will make it easier for readers to focus on the content. We will provide easier access to everyday actions to readers and editors. We will put things in logical and useful places. We will increase consistency in the interface with other platforms. We will eliminate clutter. We will make a space for future growth.

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


 * 1) We are working on the interface only. No work will be done in terms of styling templates, the structure of page contents, map support, or cross-wiki templates.
 * 2) Elements of the interface might move around, but all navigational items and other functionality currently available by default will remain.
 * 3) We have analysed many wikis and have noticed many useful gadgets. Some of them definitely deserve to be surfaced and be a part of default experience.
 * 4) Though our changes will be easily noticeable, we are taking an evolutionary approach and want the site to continue feeling familiar to readers and editors. Each feature will be discussed, developed, and deployed separately.
 * 5) Monobook, Timeless, Minerva and Modern are out of the scope of our adjustments. We will freeze the current Vector to Legacy Vector, and will deploy our features as parts of the new default Vector.

Deployment plan and timeline
'''On selected wikis, our changes will be visible as default for all users. On most wikis, the changes will be available as beta features. It will be easy for users to switch our changes off.'''


 * 1) It is important for us to receive feedback from both readers and editors. Thus, we will be deploying the changes as default to a set of testing wikis for all users.
 * 2) On all other wikis, the improvements will be available as user preferences.
 * 3) Editors on all wikis will also be provided with a quick opt-out button if they wish to use the older version of the skin.

First two features (the new header and collapsible sidebar) will be deployed in June/July 2020.

What features will be added
We have not created a complete, detailed product specification. Each feature will be built and implemented separately, over time. Features which have been created are still being adjusted and improved. Our decisions are based on community feedback, user testing, and extracted API data.

Participate
Test our features individually, share feedback, and join our early adopting wikis!