GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Main page
  • Get MediaWiki
  • Get extensions
  • Tech blog
  • Contribute
  • User help
  • FAQ
  • Technical manual
  • Support desk
  • Communication
  • Developer portal
  • Code statistics
  • Community portal
  • Recent changes

This view

  • Original page
  • New address

GeezerVison is showing www.mediawiki.org — VisualEditor - MediaWiki

Wikimedia Foundation projects
VisualEditor
Extending and improving the editing tools used at Wikimedia
Group: Contributors
Start: 2011-05-15
Team members: Editing team
Backlog: #VisualEditor
For help installing and running VisualEditor, see Extension:VisualEditor.
For changes made on this wiki using VisualEditor, see the filters visualeditor and visualeditor-switched.

VisualEditor is a reliable rich-text editor for HTML documents. It was created by the Editing team for MediaWiki's HTML+RDFa document format (generated by Parsoid) and is available as a MediaWiki extension. VisualEditor's core implementation is a standalone JavaScript library and can run without MediaWiki, Parsoid, or Node.js.

Edit #100,000,000 in VisualEditor was made in November 2022.

As of 2020, VisualEditor is enabled by default here on mediawiki.org and on most Wikipedia and Wikivoyage language editions. On remaining wikis, is available to logged-in users as an opt-in feature; since April 2023, this is directly, rather than as a Beta Feature. VisualEditor is generally not enabled for pages outside the content namespaces, such as discussion pages or template code.

More information about VisualEditor can be found on the multi-lingual VisualEditor Portal, on Wikimedia's blog, and the FAQ. Information about VisualEditor's wikitext mode is at 2017 wikitext editor.

Original rationale

The decline in new contributor growth was viewed as the single most serious challenge facing the Wikimedia movement. VisualEditor was built with the goal of removing avoidable technical impediments associated with Wikimedia's editing interface, as a necessary pre-condition for increasing the number of Wikimedia contributors. While the initial version of VisualEditor had no measurable benefits over wikitext for new contributors, research around 2019 showed people publish more non-reverted edits when shown VE on mobile (even if the share of reverts is higher); Edit Checks have since been introduced, which reduce revert rates.

Data

See VisualEditor/Data for an overview of the what we know about how people use and experience the visual editor (mobile and desktop).

History

  • Some level of exploration was done in 2010 by the Wikipedia Usability Initiative.
  • The 2011 product whitepaper published by the Wikimedia Foundation's strategic product team identified rich-text editing as one of the "Great Movement Projects". Work subsequently started in May 2011.
  • The 2011–2012 Wikimedia annual plan, released July 2011, states a goal for VisualEditor: "First opt-in user-facing production usage by December 2011, and first small wiki default deployment by June 2012".
  • The 2012–2013 Engineering Goals document sets a timeline for VisualEditor's development and deployment up to the end of June 2013.
  • The 2013–2014 Engineering Goals document lists the goals for that year.
  • VisualEditor was deployed to most users at most Wikimedia projects by the end of 2015. See VisualEditor/Rollouts for a list.
  • As of August 2026, 1,800+ bugs have been fixed and features introduced to improve peoples' experience using the visual editor.
  • Notable features and improvements introduced since 2015:
    • Rich text paste handling, including table paste
    • Table editing improvements
    • Interwiki link improvements
    • Command search (ctrl+/)
    • Find and replace, including regexes
    • Improved template editing interface with TemplateData
    • Numerous performance & IME bugs
    • Improved auto-saved
    • Edit check

Enabling VisualEditor by default for all users or for all logged-in users can be requested by contacting the Editing team's product manager.

Core module

VisualEditor is a standalone program that can be run without MediaWiki, Parsoid, or Node.js that provides a visual editor for editing HTML5 pages. It is written in JavaScript and runs in the browser.

Here are some helpful links:

  • Standalone demo
  • Documentation
  • Git repository (GitHub mirror)
  • Installation help

Developer documentation

  • Developer glossary
  • Getting started
  • Internals
  • Developer tutorial
  • Generated code documentation
  • Sequence diagram: Page Retrieval
  • Sequence diagram: Page Edit

You can speak with us in our chat channel, #mediawiki-visualeditor connect.

Dashboards

  • Usage dashboard on Superset (requires dev shell account)
  • Continuous Integration
  • Code review dashboard

Related pages

For more information on VisualEditor and its design process, see these directory pages:

  • Design portal
  • Planning and testing
  • Software
  • Feedback archives
  • Presentations
  • Usability
  • Forecasts
  • 2015 Review of Process
    • Plans and Progress
    • Report
    • Design of Backlog
  • 2016 Team Offsite and Retrospective

See also

  • A VisualEditor demo page/sandbox
  • Extension:VisualEditor (including installation instructions)
  • Guide to hacking VisualEditor: VE gadgets
  • Parsoid
  • VisualEditor/Index of related pages on several wikis
  • VisualEditor multilingual newsletter, focused on WMF wikis
  • Results of the 2015 survey
  • Slash Commands – Adds "slash commands", i.e., text shortcuts that start with a forward slash ("/") and trigger specific actions via the Visual Editor.
Retrieved from "https://www.mediawiki.org/w/index.php?title=VisualEditor&oldid=8608744"
Categories:
  • WMF Projects
  • VisualEditor
  • Libraries
  • Edit extensions
Hidden categories:
  • WMF Projects 2011q2
  • WMF Projects 2011q3
  • WMF Projects 2011q4
  • WMF Projects 2012q1
  • WMF Projects 2012q2
  • WMF Projects 2012q3
  • WMF Projects 2012q4
  • WMF Projects 2013q1
  • WMF Projects 2013q2
  • WMF Projects 2013q3
  • WMF Projects 2013q4
  • WMF Projects 2014q1
  • WMF Projects 2014q2
  • WMF Projects 2014q3
  • WMF Projects 2014q4
  • WMF Projects 2015q1
  • WMF Projects 2015q2
  • WMF Projects 2015q3
  • WMF Projects 2015q4
  • WMF Projects 2016q1
  • WMF Projects 2016q2
  • WMF Projects 2016q3
  • WMF Projects 2016q4
  • WMF Projects 2017q1
  • WMF Projects 2017q2
  • WMF Projects 2017q3
  • WMF Projects 2017q4
  • WMF Projects 2018q1
  • WMF Projects 2018q2
  • WMF Projects 2018q3
  • WMF Projects 2018q4
  • WMF Projects 2019q1
  • WMF Projects 2019q2
  • WMF Projects 2019q3
  • WMF Projects 2019q4
  • WMF Projects 2020q1
  • WMF Projects 2020q2
  • WMF Projects 2020q3
  • WMF Projects 2020q4
  • WMF Projects 2021q1
  • WMF Projects 2021q2
  • WMF Projects 2021q3
  • WMF Projects 2021q4
  • WMF Projects 2022q1
  • WMF Projects 2022q2
  • WMF Projects 2022q3
  • WMF Projects 2022q4
  • WMF Projects 2023q1
  • WMF Projects 2023q2
  • WMF Projects 2023q3
  • WMF Projects 2023q4
  • WMF Projects 2024q1
  • WMF Projects 2024q2
  • WMF Projects 2024q3
  • WMF Projects 2024q4
  • WMF Projects 2025q1
  • WMF Projects 2025q2
  • WMF Projects 2025q3
  • WMF Projects 2025q4
  • WMF Projects 2026q1
  • WMF Projects 2026q2
  • WMF Projects 2026q3
  • WMF Projects 2026q4
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.