Reading/Web/Desktop Improvements/fr

Notre interface pour ordinateurs de bureau a évolué dans le temps. Cependant, depuis l’introduction de l’habillage Vector (le design par défaut du site), la plupart de ces changements ont été conduits par des bénévoles et sont seulement disponibles sous forme de prototypes, gadgets, scripts utilisateur et habillages conçus par des bénévoles. Nous pensons qu’il est temps de prendre certaines de ces idées pour qu’ils deviennent accessibles par défaut. Pendant les deux prochaines années, l’équipe Web des lecteurs va rechercher et développer des améliorations de l’expérience sur ordinateur de bureau à partir d’études et des outils existants. Nos objectifs sont de rendre les wikis Wikimedia plus accueillants pour les nouveaux lecteurs et contributeurs, et plus faciles et rapide à utiliser pour tous (à la fois les contributeurs nouveaux et vétérans).

Ce projet en est au balbutiement des discussions. Il n’y a ni projet ni développement concrets pour le moment. Nous avons besoin de votre collaboration et de retours sur les domaines clés du problème et de vos réflexions sur le design initial plus bas.

Comment vous pouvez aider
Recherche et idées : Modifiez la section « Phase 1 : Idées de conception » ci-dessous, pour ajouter de nouvelles idées, des notes, des liens vers des discussions passées, des liens vers des gadgets/scripts existants, des liens vers de bons patrons de conception à considérer, etc.

Test individuel : Une fois le développement commencé, nous rendrons le travail en cours disponible directement via un nouvel habillage dans les préférences. Vous pourrez individuellement activer et tester les changements.

Wikis complets : Nous sommes également à la recherche de wikis qui seraient intéressés pour aider dans des tests globaux, comme changer localement l’interface par défaut pour les utilisateurs connectés. Si vous pensez que votre communauté pourrait être intéressée, n’hésitez pas à nous poser toutes vos questions, puis débutez une discussion localement, et une fois qu’un consensus local est établi, ajoutez un lien vers cette discussion sur la page de discussion.

Les commentaires et idées plus longs sont les bienvenus sur la page de discussions, dans n’importe quelle langue.

Mises à jour
Inscrivez-vous au Bulletin d’information:Mises à jour des améliorations pour ordinateur de bureau pour être notifié·e lorsque de nouvelles sous-sections sont ajoutées ici. Les étapes clés majeures seront annoncées sur tous les wikis via MassMessage.

Octobre 2019 : Étude technique phase 2
Nous avons publié les résultats de notre étude technique en préparation du début du travail sur le projet. Nous avons particulièrement travaillé à réunir plus d’informations sur les éléments suivants :
 * la possibilité de servir une version différente du site aux utilisateurs non-connectés (dans l’optique de réaliser des tests avec/sans ou des tests A/B) ;
 * la recherche et les différences entre les outils-gadgets de recherche actuels ;
 * le changement de langue et les possibilités d’améliorer le changeur de langue ;
 * T234907, une RFC technique portant sur le choix la base du code avec laquelle commencer.

Septembre 2019 : rapport de recherche de Wikimania


During Wikimania 2019, we interviewed editors with the goal of sharing the plans for our upcoming Desktop improvements project, and collecting valuable feedback on a number of preliminary design ideas. Our research consisted of user interviews, a free-form feedback exercise, and a presentation with breakout groups for more focused discussion. We have published a report and a PDF summary (in English) of the feedback we received. Overall, we received positive feedback on the focus areas selected, as well as the individual prototypes for ideas. However, we were also able to identify areas for improvements.

We will be iterating over this feedback over the next few weeks and plan on developing a prototype that we can test with a wider audience across wikis.

In the slideshow below is a sample of 19 of the ideas we tested. For more context, please read the full report and then give us feedback on the talk page!

September 2019: Desktop usage and behavior data analysis
As a part of our research process, we wanted to learn more about the way people currently use the site. In particular, how often they use available functionality such as links in the sidebar, language switching, and search. We have published our results. Overall, usage of sidebar links is low - only about 0.5% of all logged out users and 1.6% of all logged-in desktop users clicked on one of the pages linked in the sidebar. Language switching usage varied, generally based on the size of the wiki, with smaller wikis switching languages more often.

August 2019: Research and brainstorming at Wikimania


Wikimania provided us with the opportunity to speak with experienced members of our communities. Over the five days of the conference we were able to share the plans for the project, and collect valuable feedback on a number of design ideas. Our research consisted of user interviews, a free-form feedback exercise, and a presentation + brainstorming session (you can see the slide-deck we used at the side). We will soon be publishing the summary of the feedback, as well as interview session results.

August 2019: Technical Research
To explore different technical possibilities for the project, the team spent a week hacking on different approaches to a single problem - how to enable the sidebar in the desktop experience to be collapsible. We are hoping to use the results from these experiments to determine the technical architecture for the improvements, as well as the skin we would like to build these improvements within. Here is a list of the experiments themselves:


 * Building a collapsible sidebar using a fork of the vector skin
 * Building the desktop sidebar within the Minerva skin. An exploration in the question: "is there a world where we have the same skin for desktop and mobile?"
 * Building a collapsible sidebar using user styles only

Problem statements

 * 1) Wikimedia wikis do not feel welcoming
 * 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).
 * 1) Wikimedia wikis are not easy to use
 * 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).
 * 1) Wikimedia wikis’s model is not easy to understand
 * 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:

Objectifs
Voici les objectifs que nous visons :


 * rendre plus facile pour les lecteurs de se concentrer sur le contenu ;
 * améliorer l’accès aux actions quotidiennes (par exemple la recherche, le changement de langue, la modification) ;
 * mettre les choses à des endroits logiques et pratiques ;
 * augmenter la cohérence de l’interface avec les autres plateformes (web mobile et applis) ;
 * éliminer les encombrements ;
 * anticiper une croissance future.

Contraintes
Voici une liste de choses que nous voulons expressément garder en tête :


 * ne pas toucher au contenu – aucun travail ne sera effectué dans la mise en page des modèles ou du contenu des pages elles-mêmes ;
 * ne supprimer aucune fonctionnalité – les choses peuvent être déplacés, mais tous les éléments de navigation et autres fonctionnalités actuellement disponibles par défaut resteront ;
 * pas de changement drastique de la disposition — nous allons prendre une approche évolutive pour les changements et voulons que le site continue de rester familier aux lecteurs et contributeurs.

Calendrier
Voici le calendrier approximativement imaginé, susceptible d’évoluer en fonction de notre progression :


 * Phase 1 : mai – septembre 2019 : investigation et études pour déterminer où nous pouvons créer de la valeur et où se concentrer.
 * Phase 2 : juillet – novembre 2019 : développement des priorités, esquisses et prototypage des idées, début des discussions.
 * Phase 3 : octobre 2019 – janvier 2020 : test utilisateur en continu et perfectionnement du design.
 * Phases 4 et + : à déterminer.

Mesures
Ci-dessous, une ébauche des mesures essentielles que nous souhaitons réaliser durant ce projet. Au fur et à mesure que nous définissons les changements que nous voulons réaliser avec plus de précision, nous reprendrons et étendrons cette liste.

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)

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:


 * Understanding the history of the desktop interface
 * Reading previous Wikipedia research conducted by the Wikimedia Foundation or other research institutions and individuals
 * Discussions at our team offsite to develop a shared understanding of the project and generate ideas
 * Winter, Timeless, and other Wikipedia redesigns
 * Reading about redesigns/updates of other large websites (Reddit, Twitter, etc.)
 * Conducting an audit of other large websites to try and glean common structural elements

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 2019)
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.

Phase 1 : Idées de conception
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 Easier access to everyday actions Putting things in logical and useful places
 * Collapsible sections in sidebar
 * Examples: Hebrew Wikipedia, ...
 * Research: Usability initiative research on collapsible languages links, Usability initiative mockups on collapsible sections within the sidebar
 * Collapsible sidebar
 * Examples: Wide Skin (enwiki script), Hide Vector sidebar (enwiki script), Timeless skin sidebar (responsive-layout), ...
 * Floating sidebar
 * Examples: FloatSide (enwiki script), ...
 * Sticky header with search, table of contents, edit links
 * Examples: FloatHead (enwiki script), FloatHead (another enwiki script), Floater (enwiki script), Winter (historical prototype), Timeless (alternative skin), ...
 * Research: Usability-wiki
 * 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
 * Examples: Gadget-StickyTableHeaders (enwiki gadget)
 * Consolidated user menu (e.g. collapsing things like "Log out", "Preferences", and "Beta", inside a dropdown menu)
 * Examples: Compact personal bar
 * Preferences for logged out users
 * Examples: Accessibility settings/preferences (T91201), ...
 * Moving article actions from the sidebar to within the article
 * Examples: Winter, Timeless skin at 1085px or thinner, ...