![]() | |
![]() VisualEditor's text formatting menu | |
Developer(s) | Wikimedia Foundation and Wikia |
---|---|
Written in | JavaScript, Node.js, PHP |
Operating system | Cross-platform |
Platform | MediaWiki extension |
Type | Wiki |
License | MIT[1] |
Website | www |
VisualEditor (VE) is a project to provide a "visual" or "WYSIWYG-like" online rich-text editor as a MediaWiki extension to Wikipedia. It was developed by the Wikimedia Foundation in partnership with Wikia.[2] In July 2013 the beta was enabled by default, with the ability to opt-out, for Mediawiki.org and several of the largest Wikipedias.[3][4]
The Wikimedia Foundation considered it the most challenging technical project to date, while The Economist has called it Wikipedia's most significant change.[5] According to The Daily Dot, Wikimedia Foundation's pursuit of wider participation may risk alienating existing editors.[6] In September 2013, English Wikipedia's VisualEditor was changed from opt-out to opt-in, following user complaints,[7][8] but was returned to being available by default in October 2015 after further development.[9] A 2015 study by the Wikimedia Foundation found that VisualEditor failed to provide the anticipated benefits for new editors.[10]
Contents
Development
The original web-based Wikipedia editor provided by MediaWiki is a plain browser-based[note 1] text editor where authors had to learn the wiki markup language to edit.[11] A WYSIWYG editor for Wikipedia had been planned for years in order to remove the need to learn the wiki markup language. It was hoped this would reduce the technical hurdle for would-be Wikipedians, enabling wider participation in editing, and was an attempt to reverse the decline in editor numbers of 50,000 in 2006 to 35,000 in 2011, having peaked in 2007.[5][6] It was part of a $1m project aimed at developing new features and making improvements.[5] A goal of the project is to allow both the former wiki markup editing and editing with the WYSIWYG VisualEditor.[12] According to Wikimedia Foundation's Jay Walsh, the hope is to redress under-represented contributions from Arabic, Portuguese, and Indic-language versions of the site.[6][note 2]
According to Wikimedia Foundation "There are various reasons that lead existing and prospective contributors not to edit; among them, the complexity of wiki markup is a major issue. One of VisualEditor's goals is to empower knowledgeable and good-faith users to edit and become valuable members of the community, even if they’re not wiki markup experts. We also hope that, with time, experienced editors will find VisualEditor useful for some of their editing tasks."[4] In 2012, Sue Gardner, the executive director of the Wikimedia Foundation, said "we don't think that the visual editor, in and of itself, is going to solve the challenge",[13] and Wikipedia co-founder Jimmy Wales remarked "This is epically important".[14]
Rollout
MediaWiki is used by a large number of wikis, with smaller sites originally conceived as being rolled out first.[15] VisualEditor was planned to be rolled out on the English-language Wikipedia for editors with registered accounts, and then for anonymous editors.[16] The alpha version was made available to select users in December 2012, widened to all registered users in April.[17] It was default editor for users logged-into the English-language Wikipedia in July 2013.[4][6] It was subsequently made opt-in on the English-language Wikipedia in September 2013 due to community complaints over its stability and implementation was buggy and had limitations[7][8] (though it remained active for most non-English Wikipedias).[18] In 2015 it completed its beta development phase and was again made available on English Wikipedia.[9][19]
Technical
The Wikimedia Foundation joined forces with Wikia to work on the project.[20] The implementation encountered challenges with the wiki markup language (the basis for Wikipedia articles), due to it being continuously extended over 12 years to include seldom-used rich and complex features making reproduction of the final article appearance dependent on many factors that were not easy to reproduce.[21] The technical implementation required improvements to MediaWiki in parsing, wiki markup language, the DOM and final HTML conversion.[22] A necessary component is a parser server called Parsoid[note 3] which is written in Node.js and was created to convert in both directions between wikitext and a format suitable for VisualEditor.[21] The Wikimedia Foundation considered VisualEditor its most challenging technical project to date.[5]
As of April 2015 supported web browsers include modern versions of Chrome, Firefox, Midori, Opera, Safari and Internet Explorer (10+).
The VisualEditor MediaWiki extension is available for download by server operators and typically requires the latest version of MediaWiki.
Online rich-text editor
According to the VisualEditor team, the aim is "to create a reliable rich-text editor for MediaWiki",[23] a "visual editor" which is "WYSIWYG-like".[24] The implementation is split into a "core" online rich-text editor which can run independently of MediaWiki,[25] and a MediaWiki extension.[26] The MediaWiki extension is in the category "WYSIWYG extensions".
Assessments
The Daily Dot suggested that the Wikimedia Foundation's pursuit of more users may be at the risk of alienating the existing editors.[6] Some experienced editors have expressed concerns about the rollout and bugs, with the German Wikipedia community voting overwhelmingly against making the VisualEditor the new default, and expressing a preference for making it an "opt-in" feature instead.[6][27] Despite these complaints, the Wikimedia Foundation continued with the rollout to other languages.[6] The Register said, "Our brief exploration suggests it certainly removes any need to so much as remember what kind of parenthesis belongs where."[17] The Economist's L.M., said it is "the most significant change in Wikipedia's short history."[5] Softpedia ran an article titled "Wikipedia's New VisualEditor Is the Best Update in Years and You Can Make It Better".[28] Some opponents have said that users may feel belittled by the implication that "certain people" are confused by wiki markup and therefore need the VisualEditor.[29]
The Daily Dot reported on 24 September 2013 that the Wikimedia Foundation had experienced a mounting backlash from the English Wikipedia community, which criticised the VisualEditor as slow, poorly implemented and prone to break articles' existing text formatting. In the resulting "test of wills" between the community and the Foundation, a single volunteer administrator overrode the Wikimedia Foundation's settings to change the availability of VisualEditor from opt-out to opt-in. The Foundation acquiesced, but vowed to continue developing and improving the VisualEditor.[7][8]
Research results
The Wikimedia Foundation ran a controlled study on the effects of VisualEditor in May 2015. The study found that VisualEditor did not increase the number of newcomers who successfully begin editing, did not increase their productivity, and did not increase new editor retention. Editing took significantly longer with VisualEditor, and new editors were less likely to save their work.[10] A previous June 2013 controlled test — when VisualEditor was less mature — showed similar neutral and negative results.[30]
See also
Notes
References
- ^ LICENSE.txt Archived 2018-01-12 at the Wayback Machine, VisualEditor source code repository, phabricator.wikimedia.org/diffusion/
- ^ Andrew Webster (2012-06-22). "Wikimedia releases updated prototype for simplified visual editor". The Verge. Archived from the original on 2013-09-27. Retrieved 2013-07-27.
- ^ "Wikipedia:VisualEditor". Wikipedia. Retrieved 15 September 2013.
- ^ a b c Emil Protalinski (2013-07-02). "Wikimedia rolls out WYSIWYG visual editor for logged-in users accessing Wikipedia articles in English". The Next Web. Archived from the original on 2013-07-05. Retrieved 2013-07-06.
- ^ a b c d e L.M. (2011-12-13). "Changes at Wikipedia: Seeing things". The Economist. Archived from the original on 2013-06-09. Retrieved 2013-07-28.
- ^ a b c d e f g Tim Sampson (2012-07-04). "Will Wikipedia's pretty new editing software solve its recruitment crisis?". The Daily Dot. Archived from the original on 2013-09-27. Retrieved 2013-07-27.
- ^ a b c Andrew Orlowski (2013-09-25). "Revolting peasants force Wikipedia to cut'n'paste Visual Editor into the bin". The Register. Archived from the original on 2013-10-01. Retrieved 2013-10-06.
- ^ a b c Tim Sampson (2013-09-24). "Wikipedia faces revolt over VisualEditor". The Daily Dot. Archived from the original on 2013-09-25. Retrieved 2013-09-25.
- ^ a b Forrester, James (2015-09-01). "Gradual availability of VisualEditor for new users is now complete". Wikipedia, the free encyclopedia.
- ^ a b "VisualEditor's effect on newly registered editors/May 2015 study". Wikimedia.org. Wikimedia Foundation. Retrieved 2 August 2016.
- ^ Martin Brinkmann (2012-02-24). "Wikipedia Visual Editor Coming Soon". ghacks. Archived from the original on 2013-09-27. Retrieved 2013-07-28.
- ^ ehe (2011-12-14). "Wikimedia testing visual editor". h-online. Archived from the original on 2013-07-27. Retrieved 2013-07-28.
- ^ Megan Garber (2012-07-12). "On the Ugliness of Wikipedia". The Atlantic. Archived from the original on 2013-07-03. Retrieved 2013-07-29.
- ^ Gene Ryan Briones (2012-06-21). "Wikimedia launches new prototype "visual editor" for Wikipedia". ubergizmo.com. Archived from the original on 2013-09-29. Retrieved 2013-07-29.
- ^ Jamie Keene (2011-12-15). "Wikimedia Foundation previews simplified visual editor". The Verge. Archived from the original on 2013-09-28. Retrieved 2013-07-28.
- ^ Gabriela Vatu (2013-06-06). "Wikipedia's Visual Editor to Be Rolled Out". Softpedia. Archived from the original on 2013-06-15. Retrieved 2013-07-06.
- ^ a b Simon Sharwood (2013-06-07). "Wikimedia edges closer to banishing Wikitext". The Register. Archived from the original on 2013-07-28. Retrieved 2013-07-28.
- ^ "VisualEditor". Archived from the original on 2013-09-27.
- ^ "Wikimedia Engineering 2015 Q1 Goals". mediawiki.org. Retrieved 2018-10-24.
- ^ "VisualEditor - the past, present and future". Wikia Community Central. Archived from the original on 2015-12-08. Retrieved 2015-12-02.
- ^ a b djwm (2012-12-13). "VisualEditor launched in Wikipedia". h-online. Archived from the original on 2013-07-27. Retrieved 2013-07-28.
- ^ Sumana Harihareswara, Guillaume Paumier. "The Architecture of Open Source Applications (Volume 2) : MediaWiki". aosabook.org. Archived from the original on 2013-09-24. Retrieved 2013-07-27.CS1 maint: Uses authors parameter (link)
- ^ "VisualEditor". Archived from the original on 2013-09-27.
- ^ "VisualEditor:Welcome". Archived from the original on 2015-04-03.
- ^ "wikimedia/VisualEditor". GitHub.
- ^ "Archived copy". Archived from the original on 2015-08-11. Retrieved 2015-05-29.CS1 maint: Archived copy as title (link)
- ^ Andrew Orlowski (2013-08-01). "Wikipedians say no to Jimmy's 'buggy' WYSIWYG editor". The Register. Archived from the original on 2013-08-04. Retrieved 2013-08-05.
- ^ Lucian Parfeni (2013-07-02). "Wikipedia's New VisualEditor Is the Best Update in Years and You Can Make It Better". Softpedia. Archived from the original on 2013-10-03. Retrieved 2013-07-30.
- ^ Simonite, Tom (October 22, 2013). "The Decline of Wikipedia: Even As More People Than Ever Rely on It, Fewer People Create It". MIT Technology Review. Archived from the original on October 23, 2013. Retrieved January 17, 2014.
- ^ "Research:VisualEditor's effect on newly registered editors/June 2013 study". Wikimedia.org. Wikimedia Foundation. Archived from the original on 10 September 2016. Retrieved 10 August 2016.
Further reading
- Roth, Amy; Davis, Rochelle; Carver, Brian (2013). "Assigning Wikipedia editing: Triangulation toward understanding university student engagement". First Monday. 18 (6). doi:10.5210/fm.v18i6.4340.
- Florian Leander Mayer. "Erfolgsfaktoren von Social Media: Wie "funktionieren" Wikis?: Eine vergleichende Analyse kollaborativer Kommunikationssysteme im Internet, in Organisationen und in Gruppen" (2013) Lit Verlag, pp. 30–32. ISBN 978-3643122100