 |
This article needs to be updated. The reason given is: it still is used a decade on, but the article is stuck in the 2010s. Please help update this article to reflect recent events or newly available information. (January 2023)
|
VisualEditor logo, set in Gill Sans
| |
VisualEditor's text formatting menu
| |
| Developer(s) | Wikimedia Foundation and Fandom, Inc. |
|---|---|
| Written in | JavaScript, Node.js, PHP |
| Operating system | Cross-platform |
| Platform | MediaWiki extension |
| Type | Wiki |
| License | MIT[1] |
| Website | www |
VisualEditor (VE) is an online rich-text editor for MediaWiki-powered wikis that provides a direct visual way to edit pages based on the "what you see is what you get" principle. It was developed by the Wikimedia Foundation in partnership with Fandom.[2] In July 2013, it was enabled by default on several of the largest Wikipedia projects.[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, the 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 it was returned to being available by default (for new registered users only) 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]
The original web-based Wikipedia editor provided by MediaWiki is a plain browser-based text editor, also called 'Source editor', where authors have to learn the wiki markup language to edit.[11] A what you see is what you get (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 1]
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]
MediaWiki is used by numerous 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 the 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]
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 2] which 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 January 2021[update] supported web browsers include modern versions of Chromium (Chrome, Edge, Opera), Firefox, Midori, and Safari.[citation needed]
The VisualEditor MediaWiki extension is available for download by server operators and typically requires the latest version of MediaWiki, it is bundled since MediaWiki 1.35.[23]
According to the VisualEditor team, the aim is "to create a reliable rich-text editor for MediaWiki",[18] 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]
Responses to the introduction of the VisualEditor have greatly varied, with The Economist's L.M. calling it "the most significant change in Wikipedia's short history."[5]
Some editors expressed concerns about the rollout and bugs, with the German Wikipedia community deciding to use an opt-in model instead of an opt-out one.[6][27] Irish Wikipedia administrator Oliver Moran, echoing concerns of other editors, said that users may feel belittled by the implication that "certain people" are confused by wiki markup and therefore need the VisualEditor, comparing the learning of wikitext favorably to Twitter's hashtag and @ (at sign) mention syntax.[28]
Three months after the rollout of the VisualEditor to the English Wikipedia, The Daily Dot reported that the Wikimedia Foundation had experienced backlash from long-time editors who deemed the editor "buggy and untested". Following discourse between the community and the foundation, Wikipedia administrator Kww overrode the foundation's rollout, making it opt-in, instead of opt-out. The Foundation did not revert the change, instead committing to further improving VisualEditor.[7][8]
Softpedia ran an article titled "Wikipedia's New VisualEditor Is the Best Update in Years and You Can Make It Better".[29] The Register said that the update brings the foundation "a little closer to its goal of making it easier for anyone to create and edit Wikipedia articles."[17]
 |
This section relies excessively on referencestoprimary sources. Please improve this section by adding secondary or tertiary sources.
Find sources: "VisualEditor" – news · newspapers · books · scholar · JSTOR (January 2022) (Learn how and when to remove this message) |
Aaron Halfaker, a research scientist at the Wikimedia Foundation, ran a controlled study on the effects of VisualEditor in May 2015. The study found that VisualEditor did not increase editor productivity, however reducing the burden upon existing editors. Editing took 18 seconds longer with VisualEditor before hitting save, and new editors were less likely to save their work. Halfaker however did ascribe these negative results as from editors testing the new system, not any real struggle.[10] A previous June 2013 controlled test — when VisualEditor was less mature — showed similar neutral and negative results.[30]
|
| |||||||
|---|---|---|---|---|---|---|---|
| Overview (outline) |
| ||||||
| Community (Wikipedians) |
| ||||||
| History |
| ||||||
| Honors |
| ||||||
| References and analysis |
| ||||||
| Mobile |
| ||||||
| Content use |
| ||||||
| Related |
| ||||||
| |||||||
