2017 wikitext editor/es

frameless|600px El editor de wikitexto 2017 es un modo del Editor visual que permite utilizar las herramientas y la barra de herramientas del editor visual para editar el código fuente del wikitexto. Se puede acceder a él desde el editor haciendo clic en la barra de herramientas para cambiar a wikitexto.

Se puede activar en las wikis de Wikimedia como función en fase de pruebas desde tus preferencias.

Qué es
En aras de alcanzar uno de los objetivos del Plan Anual 2016-2017, «Mantener y mejorar gradualmente la creación actual de contenidos y las interfaces de control», el Departamento de edición está trabajando en un nuevo editor de wikitexto. Está integrado en el editor visual para facilitar el cambio entre ambos. Presenta un diseño semejante, así como muchas de las herramientas presentes en el editor visual, incluido el servicio citoid. El nuevo modo de edición de wikitexto está disponible como una función en fase de pruebas para los usuarios de equipos de sobremesa. La tarea principal correspondiente en Phabricator es T104479 (donde pueden referirse al mismo como «editor de wikitexto moderno» o «nuevo editor de wikitexto»/«NWE»).

Este editor es «nuevo», y no una modificación del anterior. Se ofrece como función en fase de pruebas con el objeto de que los usuarios puedan evaluarla y evitar el cese repentino de los editores y el desajuste de los gadgets que están en uso actualmente.

Cuáles son las motivaciones tras este proyecto
En 2010, la Fundación Wikimedia dio por concluido el proyecto de Usabilidad (que introdujo la apariencia Vector, la herramienta de subida de archivos y el editor de contenido) y pasó a ocuparse de los problemas seleccionados por la comunidad para el Plan Estratégico 2010-2015. Con ello se incluyeron varias mejoras en las herramientas de edición, principalmente en el editor visual, además del sistema de notificaciones y otras. Aun así, el planteamiento inicial nunca ha sido reemplazar el wikitexto; se considera a largo plazo que ambos sistemas de edición (código y visual) son fundamentales para permitir a la comunidad continuar trabajando en los proyectos de Wikimedia con el mismo éxito que se ha conseguido hasta la fecha.

A partir de diciembre de 2016, en la mayoría de las wikis de Wikimedia se empezaron a ofrecer tres editores de contenido. Los tres son considerablemente diferentes en apariencia y modo de funcionamiento, tanto para los usuarios como a nivel técnico, además de contar con un soporte y ayuda distintos. Uno de ellos es el editor de wikitexto para equipos de sobremesa de la década de 2010 denominado WikiEditor, otro es el editor visual tanto para móviles como para equipos de sobremesa y el último es el editor de wikitexto minimalista para móviles.

Desde 2010 se ha aprendido mucho sobre cómo emplean los usuarios, tanto los nuevos como los veteranos, el software y cómo les gustaría que funcionase. Se ha investigado sobre el diseño óptimo del editor visual para que funcione tal y como los editores desearían, siendo amigable para los nuevos usuarios sin estorbar a los veteranos. A pesar de todo ello, se han detectado marcadas preferencias por parte de los nuevos usuarios respecto al diseño del editor visual, sugerencias sobre el sistema de funcionamiento y de la experiencia global. También se ha aprendido mucho sobre las soluciones técnicas implementadas en las páginas (como cuando se pulsa sobre "") o en las herramientas (como en Flow) y sobre el acceso desde equipos de sobremesa y móviles, y la manera en que se aplican a otras características.

Having three inconsistent editing systems is bad. It is bad for newbies, because whatever ideas they've learnt from one editor can't be applied to other contexts (like editing a talk page). It is bad for existing editors, who have to jump through several questions before they can work out what the situation for the newbie is and so how to help. It is bad for sysops, who need to separately set up what their community needs in each of the editors – or find out that they can't get it in some editors. It is bad for script and gadget developers, who have to deal with lots of different situations (or ignore them). It is bad for developers, who have to take three times as many parts of complexity into account whenever they need to fix something or add a feature. And it is bad for the donors to the Wikimedia Foundation, whose donations are spent supporting these multiple parallel work streams.

Consequently, we're working on a new wikitext editor. This will provide a single, integrated, consistent experience between desktop and mobile, and wikitext and visual editors. It will be a platform that can be integrated into other editors, so that the experience can be as close as possible between situations and content types. We'll give users as good an experience as we can, without breaking anything.

Please note that the current phase of deployment is providing this as a Beta Feature and getting feedback. Only once we've met our quality requirements (including new-user testing and experienced-user happiness), probably in mid-2017, we'll begin to provide it by default in place of the current wikitext editor. Users who don't like it will of course be able to not use it whilst it's a Beta Feature, and to disable it along with the visual editor once it's released to everyone. The current wikitext editor is not going anywhere, at least for the next few years. While we may eventually sunset it, anyone who likes it can keep it.

First release (Beta Feature)
The initial goals for the project were to have parity with the existing wikitext editor, WikiEditor, using the same toolbar with the same buttons in the same positions as in the visual editor so users have consistent experience. This means providing at least all the controls in the wikitext editor, with very few exceptions for very rare buttons:


 * Basic tools (bold, italics, signature, links and images);
 * Advanced tools (headings, bullet lists, numbered lists, big, small, superscript and subscript, galleries and tables);
 * Special character insertion; and
 * Find-and-replace.

All these were completed as of August 2016, along with a lot of tools not in the existing wikitext editor (like strikethrough, underline, template inserting and so on), and features like pasted HTML being turned into wikitext automatically. In particular, we also provide the "citoid" auto-citation tool, which lets users quickly add references based on URLs or DOIs. This is similar to, but more advanced than, the gadgets that a few wikis like the English Wikipedia had written for themselves already, and they will now be available for all wikis.

We undertook extensive QA testing that the features work as expected, and a design review and structured user testing. Once we were happy that it is adequately working as intended, and is (at least) no worse for new users, we have sought feedback from experienced users of all levels via a Beta Feature.

Final beta release (before general release)
The point of the first release as a beta feature is to get some initial feedback on how well this new editor works for people. We expect the feedback to include a lot of suggestions for changes. There are a number of improvements that we're already considering. Some of these probably need to be addressed before the new wikitext editor would be released outside of a beta feature. Some of these are technically difficult and so have been postponed, whilst others would benefit from real-world feedback from existing users to shape the features as usefully as possible.

For the first category (big challenges), we believe that we will need to address section editing, in which clicking edit will show small parts of the page to edit, and a fully responsive design, so that the interface can scale up and down more cleanly for smaller devices, where users are zoomed-in, or other accessibility and platform reasons; these will let us provide the feature in mobile as a beta example as well, to ensure it works for all our editors, not just those on desktop.

For the second category (feedback needed), we will need to provide in-editor help to guide users through the editing process from the very first time they click edit and also later in their editing careers. Right now the wikitext editor has a "help" tab with some brief wikitext guidance; in the visual editor, we have a link to the user-guide, which we could replicate for this purpose. How this should work, and what it should highlight, is likely to be something on which many members of our communities have expert ideas. We will also need to clean up how gadgets extend the editor, as the new editor integration right now is complex and confusing. This would make converting some gadgets harder than it should be. Many wiki communities depend on particular gadgets to speed up their editing workflow, and it's important that we preserve the ability for wikis to flexibly experiment with improvements like this.

Naturally, any change of this scale is likely to be disruptive for some users' workflows, and will have a few issues with relative 'edge cases' not being addressed. We look forward to uncovering and addressing these over the weeks and months following the release of the beta feature.

Nice-to-haves
Alongside the above, there are other, new features we'd love to provide if possible, but which may prove too costly to develop or too slow for users, and so are not planned from the outset. One feature we'd be interested in providing is saving automatic local drafts as users edit, so that if their browser or computer crashes or loses power mid-edit they can resume rather than having to restart. This would rescue users from quite frustrating, if uncommon, occurrences, particularly people with poorly/old computers or network connections.

A big feature that often gets discussed is syntax highlighting of wikitext to help guide people's eyes to the right content for which they're looking. This feature was in fact built for the existing wikitext editor back in 2011, but we had to abandon it because the very high complexity of wikitext means that this was exceedingly slow for most users. Five years later, most users' machines are a fair bit faster than they were back then, which helps a little. Also, it might be worth exploring how performant we could make a feature doing this if we were to make some simplifications of the kinds of wikitext which we try to highlight.

More complex and error-prone than syntax highlighting, but possibly even more useful, would be a feature for folding wikitext structures into blocks so that users can easily ignore things they don't want to edit without having to read through them. For example, long infobox invocations or references could be folded up into blocks until you want to edit them. The technologies we built for the visual editor are particularly well-suited for providing this use case in a reliable fashion, so this may be something we could look at doing. Again, as with syntax highlighting we might need to compromise on the complexity of wikitext that we recognise in return for providing something performant enough to be useful to most of our users.

Another nice feature we could provide would be to prompt users when they save with two or three buttons to add one-click edit summaries based on their recent activities. This kind of feature is quite popular on some wikis as a gadget and it would be nice to provide it to all users on all wikis, without those wikis needing to have a gadget guru on hand to help set it up and maintain it.

Resources

 * An early rough design mockup from April is available here. To see the wikitext editor, click the brackets icon in the top-right corner.
 * An old rough demo video is also available as of mid-May 2016 at https://www.youtube.com/watch?v=jgd2ZHOZGBE.
 * Video demo of the 2017 wikitext editor from the December 2016 CREDIT showcase
 * The current version can be seen via Beta Features at https://www.mediawiki.org/wiki/Special:Preferences#mw-prefsection-betafeatures; enable the "new wikitext editor" item, go to https://www.mediawiki.org/wiki/Project:Sandbox?veaction=editsource (for example) and see what it looks like when you switch back and forth.