Reading/Web/Desktop Improvements/id

Sudah 10 tahun sejak skin default Wikimedia (Vektor) digunakan. Selama dekade terakhir, antarmuka telah diperkaya dengan ekstensi, gadget, dan skrip pengguna. Sebagian besar tidak terkoordinasi secara visual atau lintas-wiki. Pada saat yang sama, desain web, serta ekspektasi pembaca dan editor, telah berkembang. Kami pikir inilah saatnya untuk mengambil beberapa ide ini dan membawanya ke pengalaman default semua pengguna, di semua wiki, dengan cara yang teratur dan konsisten. Selama beberapa tahun ke depan, tim web pembaca akan meneliti dan membangun peningkatan pengalaman desktop berdasarkan penelitian dan alat yang ada.

Tujuan kami adalah membuat wiki Wikimedia lebih ramah dan meningkatkan utilitas di antara pembaca dan memelihara utilitas untuk editor yang ada. Kami akan mengukur peningkatan kepercayaan dan sentimen positif terhadap situs kami, dan kegunaan situs kami (penggunaan tindakan umum seperti penelusuran dan peralihan bahasa).

Awalnya, di sebagian besar wiki, hanya pengguna yang masuk yang dapat ikut serta satu per satu. Pada wiki terpilih, perubahan kami akan diterapkan untuk semua secara default, dan pengguna yang masuk akan dapat memilih keluar. Kami berharap untuk meningkatkan kumpulan wiki  pengadopsi awal  secara bertahap, hingga peningkatan kami menjadi default di semua wiki pada tahun 2021.

Saat ini, antarmuka…
'''…tidak sesuai dengan harapan. …berantakan dan tidak intuitif. …tidak menyoroti sisi komunitas. …tidak konsisten dengan versi seluler.'''


 * 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 users from focusing on what they came for. It is challenging for readers to focus on the content. It is not possible for them to intuitively switch languages, search for content, or adjust reading settings. New editors are 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 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.

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 are easily noticeable, we are taking an evolutionary approach and want the site to continue feeling familiar to readers and editors. Each feature is discussed, developed, and deployed separately.
 * 5) 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.

Deployment plan and timeline
Test our features individually, share feedback, and join our early adopter wikis!


 * 1) It is our intention to test our improvements in collaboration with a diverse set of volunteering early adopter wikis, both Wikipedias and sister projects.
 * 2) Both prior to development and after deployment, we will be collecting data (via A/B testing, prototype feedback rounds, etc.). In the case of significantly negative results, we will roll back our changes.
 * 3) First three features (the new header, collapsible sidebar, and limiting content width) were deployed in July 2020. Our hope is to develop a few more features until the end of 2020.
 * 4) We are hoping to increase the set of early adopter wikis gradually, until our improvements are default on all wikis in 2021.

List of early adopter wikis (test wikis)

 * eu:
 * fr:
 * 
 * he:
 * fa:
 * 
 * Office Wiki

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.