Reading/Web/Desktop Improvements/fi

Nyt on kulunut yli kymmenen vuotta siitä, kun Wikimedian nykyinen oletusulkoasu Vektori otettiin käyttöön. Viimeisen vuosikymmenen aikana käyttöliittymää on rikastettu laajennuksilla, gadgeteilla ja käyttäjäskripteillä. Suurinta osaa niistä ei ole koordinoitu visuaalisesti tai wikienvälisesti. Samaan aikaan sekä verkkosuunnittelu että lukijoiden ja muokkaajien odotukset ovat kasvaneet ja kehittyneet. Mielestämme on aika ottaa joitain näistä ideoista ja tuoda ne kaikkien käyttäjien oletusnäkymään, kaikkiin wikeihin, järjestäytyneellä ja johdonmukaisella tavalla. Over the last decade, the interface has been enriched with extensions, gadgets and user scripts. Most of these were not coordinated visually or cross-wiki. At the same time, web design, as well as the expectations of readers and editors, have evolved. We think it's time to take some of these ideas and bring them to the default experience of all users, on all wikis, in an organized, consistent way. Over the next couple of quarters, the readers web team will be researching and building out improvements to the desktop experience based on research and existing tools.

Our goals are to make Wikimedia wikis more welcoming and to increase the utility amongst readers and maintain utility for existing editors. We measure the increase of trust and positive sentiment towards our sites, and the utility of our sites (the usage of common actions such as search and language switching).

Currently, on most wikis, only logged-in users are able to opt-in individually. On selected wikis, our changes are deployed for all by default, and logged-in users are able to opt-out. We are hoping to increase the set of early adopter wikis gradually, until our improvements are default on all wikis in July 2022.

Tällä hetkellä käyttöliittymä...
'''…ei vastaa odotuksia. …on sotkuinen eikä kovinkaan intuitiivinen. …doesn't highlight the community side. …ei ole yhdenmukainen mobiiliversion kanssa.'''


 * 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) Vain hyvin pieni osa lukijoista todella ymmärtää Wikimedian wikien toimintaa. Suuri osa lukijoista ei tiedä lainkaan lukevansa vapaaehtoisten lisäämää ja säännöllisesti päivittämää sisältöä eikä tiedä voivansa itsekin osallistua muokkaamiseen.
 * 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.

Periaatteet
'''Emme koske lainkaan sisältöön. Emme poista yhtäkään toiminnallisuutta. Koskemme vain ja ainoastaan Vektori-ulkoasuun. We are inspired by the existing gadgets. We do not make major changes in single steps. '''


 * 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) 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.
 * 3) Elements of the interface might move around, but all navigational items and other functionality currently available by default will remain.
 * 4) 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.
 * 5) 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.
 * 6) Both prior to development and after deployment, we collect data (via A/B testing, prototype feedback rounds, etc.). In the case of significantly negative results, we will roll back our changes.
 * 7) It is our intention to test our improvements in collaboration with a diverse set of volunteering early adopter wikis, both Wikipedias and sister projects.

Deployment plan and timeline
We would like our improvements to be default on all wikis in July 2022.

Get involved & Contact

 * Test individually: in Preferences, check the option . You can also enable our changes using the Global preferences.
 * Join online meetings with us: until late July, we'll be organizing meetings every 2-3 weeks. Tentative dates: 6, 6, 7, 7.
 * Promote: Inform your community. Share our updates and blog posts.
 * Report bugs: to report a bug, create a task in Phabricator and add project.
 * Early adoption: We are hoping to increase the set of early adopter wikis gradually. Do you think your community might be interested in having our interface as default? Please contact us!
 * Early adoption: We are hoping to increase the set of early adopter wikis gradually. Do you think your community might be interested in having our interface as default? Please contact us!


 * Translate: help us translate related pages:

What features will be added
We have not created a complete, detailed product specification. Each feature is 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.