Reading/Web/Desktop Improvements/es

Nuestra interfaz de escritorio se ha modificado a lo largo de los años; sin embargo, desde que se presentó la apariencia Vector (el diseño predeterminado del sitio), muchos de esos cambios los han llevado a cabo voluntarios y están disponibles únicamente como prototipos, scripts de usuario, accesorios y apariencias mantenidas por voluntarios. Creemos que es hora de que llevemos algunas de esas ideas a la experiencia por omisión. Durante los próximos dos años, el equipo de lectores web realizará investigaciones y creará mejoras a la experiencia de escritorio basadas en esas investigaciones y herramientas existentes. Nuestras metas: hacer que los wikis de Wikimedia sean más acogedores tanto para los lectores nuevos como para los editores, así como más fáciles de usar y más veloces para todos (para editores nuevos y veteranos).

Este proyecto se encuentra en las primeras etapas de debate. No existe aún ningún plan concreto. Necesitamos de su colaboración y comentarios relativos a las áreas focales del problema; asimismo, queremos sus reflexiones respecto a las ideas iniciales de diseño que presentamos a continuación.

Cómo ayudar
Feedback: Please look through these details and subpages, and share your feedback on the talkpage about the ideas and mockups we have collected so far - How could they be further improved? What important considerations are not currently documented?

Research and ideas: Please edit the "Phase 1: Design ideas" sections below, to add new ideas, notes, links to past discussions, links to existing gadgets/scripts, links to good external design-patterns to consider, etc.

Individual testing: Once development begins, we will make the ongoing work available directly via a new skin option in Preferences. You will be able to individually opt-in and test the changes.

Whole wikis: We are also looking for any wikis that are interested in helping with widespread testing, such as changing the local default for logged-out site users. If you think your community might be interested, please ask us if you have any questions, then start a local discussion, and once there is local consensus add a link to that discussion on the talk page.

Siéntase libre de externar comentarios y reflexiones en la página de discusión, en cualquier idioma.

June 2020: Collapsible sidebar on officewiki, new header, and feature descriptions
Last week, we deployed our collapsible sidebar on officewiki and testwiki. You can see it by going to either of those projects, or by appending the url parameter ?useskinversion=2 to the url on any project.

In addition, we have published more details on the collapsible sidebar and header and logo changes, including in-depth feature descriptions and analysis and measurement plans.

May 2020: First deployment - officewiki and testwiki
This Monday we deployed the first visual change of the improved version of the desktop skin on our first production wikis - Officewiki (used internally by the WMF) and Testwiki (for general testing purposes). On these wikis, you will notice a reconfiguration of the project logo which is the first portion of our improved header. You can also turn the updated skin version on and off from the sidebar and your user preferences. In the next couple of weeks, we will also be deploying a collapsible sidebar for these wikis, followed by a deployment of these changes to our full set of test wikis.

We have also introduced a query string parameter using which you can see the state of the Vector skin on any wiki by adding the parameter ?useskinversion=2 to the url. Ejemplo: Paris on French Wikipedia

Subscribe to our Newsletter and check the previous updates.

Planteamientos de problemas

 * 1) Los wikis de Wikimedia no son acogedores
 * 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) Los wikis de Wikimedia no son fáciles de utilizar
 * 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) No es fácil entender el modelo de wikis de Wikimedia
 * 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.

Resumen por audiencia:

Metas
Here are the outcomes we're working towards:


 * Make it easier for readers to focus on the content
 * Provide easier access to everyday actions (e.g. search, language switching, editing)
 * Put things in logical and useful places
 * Increase consistency in the interface with other platforms - mobile web and the apps
 * Eliminate clutter
 * Plan for future growth

Limitaciones
Here is a list of things we would explicitly like to keep in mind:


 * Not touching the content - no work will be done in terms of styling templates or to the structure of page contents themselves
 * Not removing any functionality - things might move around, but all navigational items and other functionality currently available by default will remain
 * No drastic changes to the layout - we're taking an evolutionary approach to the changes and want the site to continue feeling familiar to readers and editors

Cronograma
Este es el cronograma aproximado que hemos planificado. Se modificará a medida que se haga progreso:


 * Fase 1: mayo @– septiembre 2019: Investigación y búsqueda, imaginando dónde podemos crear valor, encontrando el foco de atención.
 * Fase 2: julio @– noviembre 2019: Desarrollo de áreas de foco, haciendo bocetos y prototipos de ideas, empezando conversaciones.
 * Fase 3: octubre 2019 @– enero 2020: Contínuo testing de usuario y refinamientos de diseño.
 * Phase 4: January 2020 - May 2020: Prototype feedback and iteration. Building out first features - new header and collapsible sidebar. Deploying header to Office Wiki and Test Wiki
 * Phase 5: May 2020 - July 2020: Prototype, user test, and ship header and collapsible sidebar features to test wikis as default. Deploy header and collapsible sidebar features to all wikis as an opt-in preference
 * Phase 6+: July 2020 - TBD: Continuing with feature sequence

Test Wikis
In late 2019, we reached out to a set of wikis asking for volunteers to be test wikis for this project. We received confirmation from several of these wikis and formed a list of wikis we thought would be a good fit. When selecting test wikis, we wanted to focus on representation across wikis of various sizes, languages, and scripts. We also wanted to ensure that at least one non-Wikipedia project is selected. Based on the above criteria, the current list of test wikis is:


 * Office Wiki
 * Office Wiki
 * Office Wiki
 * Office Wiki
 * Office Wiki
 * Office Wiki
 * Office Wiki

Throughout the course of the project, we would like to increase the number of test wikis. If your community is interested in participating, please let us know on the project talk page. We will be beginning deployments at the end of March, 2020. For more details, visit the timeline.

Métricas
Below is a draft of the core metrics we want to measure through the course of the project. As we define the changes we want to make with more specificity, we will expand and iterate on this list.

Increase utility among our existing audiences, proxied by:


 * Interacciones
 * Aumentar las búsquedas por sesión un 5 % por lo que dure el proyecto
 * Aumentar los cambios de idioma por proyecto un 5 % por lo que dure el proyecto
 * Afinidad
 * Aumentar los sentimientos positivos y la percepción de familiaridad del sitio (lo cual se medirá con encuestas y pruebas con usuarios)
 * Aumentar los sentimientos de confianza y credibilidad (medibles con encuestas y pruebas con usuarios)

Feature Sequence
This is a summarized overview of the features we are considering adding or iterating on throughout the course of the project. A more detailed list is available on a separate page - we encourage looking through that page for more information. As we go through with design, requirements gathering, and user testing for each feature, we will also publish a separate page per feature with more detail. These will be linked from the title of the feature.


 * 1) New Header
 * 2) Collapsible Sidebar
 * 3) Moving language links to the article title bar
 * 4) Sticky site and article headers
 * 5) User Menu
 * 6) Improved search
 * 7) Improved language switching
 * 8) Table of contents
 * 9) Article tools
 * 10) General aesthetic refinements

Proceso de investigación y diseño
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.

Fase 1.ª: investigación y estudios, dilucidamiento de áreas donde podríamos generar valor, búsqueda de enfoques (mayo-septiembre de 2019)

 * Página principal: /Investigación y diseño: fase 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:


 * Creación de un entorno más centrado y «tranquilo» para la lectura mediante la consolidación o plegamiento opcional de enlaces de navegación, incluidos:
 * Navegación principal de barra lateral
 * Herramientas de artículo
 * Herramientas personales
 * Cambio de idioma
 * Búsqueda
 * Navegación del artículo/sumario

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)

 * Página principal: /Investigación y diseño: fase 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 2020)
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.

Fase 1.ª: ideas de diseño
Algunas de las muchas ideas que se han sugerido figuran a continuación. Añada cualquier idea importante que conozca, así como cualquier enlace:

NOTA para editores:
 * Editen la versión en inglés para añadir ideas y enlaces, o comenten en la página de discusión.
 * No se preocupe por las marcas «tvar» si no las conoce. Las añadiremos después.

Focusing on the content, distinguish content from user-interface

 * 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), WikiWand, mobileVector (mediawikiwiki gadget), CollapsibleSidebar (kowiki default gadget), ...
 * Floating sidebar
 * Examples: FloatSide (enwiki script), ...
 * Tabs in sidebar to organise all the tools and navigation: 1) TOC, 2) Site navigation, 3) Tools (for editing, page info, gadgets), 4) Bookmarks (feature request)
 * The tab icons serve also to collapse/reveal the sidebar.
 * TOC in sidebar: fixed to the screen, separately scrolled.
 * Example: WikiWand
 * Pin-able infobox: show a pin icon in top-right corner of the infobox. When pushed, pin the infobox on the right side of the screen in a column that stays on-screen and scrolls on its own, similar to the sidebar on the left.
 * Collapsible article sections: see at the bottom of the WikiWand page + add a short scrolling effect.
 * Responsive width
 * Responsive content (enwiki/mw gadget), 3 column CSS (personal css),

Easier access to everyday actions

 * 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)
 * Jump to the top of the page
 * Examples: ToTopButton (enwiki script)
 * Paragraph (¶) symbols on headings: visible only when hovering, next to the edit icon, to easily copy links to sections.

Putting things in logical and useful places

 * Consolidated user menu (e.g. collapsing things like "Log out", "Preferences", and "Beta", inside a dropdown menu)
 * Examples: Skin:Timeless, 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, ...
 * Easily navigate through articles - load page content using JS in background without loading the whole page
 * Examples: RevisionSlider, an extension to easily navigate through diffs, and Weekipedia.