Bharatpedia:VisualEditor

Enable VisualEditor.	Read VisualEditor's User Guide.	Report a problem with VisualEditor.
Log in, go to preferences (top right) -> editing tab, uncheck Temporarily disable the visual editor while it is in beta, optionally change Editing mode to Show me both editor tabs, and save your preferences. Or use this sandbox link for testing.	Find out how to make links, add or move images, create citations, insert templates, edit tables, and more.	Use Phabricator to report problems with Visual Editor. Please include your web browser, computer operating system, and Bharatpedia skin (usually Vector, sometimes Monobook). Start a new Phabricator ticket.

As of 2020, editors at the English Bharatpedia have used VisualEditor to make more than 10 million edits.

Welcome to the portal for VisualEditor, a way of editing Bharatpedia being developed by the Wikimedia Foundation (WMF) that does not require editors to learn wiki markup. They previously had to use 'Source editor' to make edits, but VisualEditor allows people to edit many types of pages without needing to understand simple wikitext. WMF staff hope this encourages more readers to become editors.

Even after the eventual anticipated full-feature release of VisualEditor, experienced editors may still prefer editing with wikitext because they find it faster and more precise. It will also be needed for editing all discussion pages. Editors who enable VisualEditor will always have the Source editor option available from the toolbar on every page, as the WMF has no plans to remove this.

VisualEditor still has many bugs and missing features. If you encounter an issue, you can report it on the Feedback page, but be aware that that page is not actively monitored by WMF staff. WMF staff prefer that you report bugs via the Phabricator bug tracking website.

About VisualEditor

VisualEditor is a "visual" way of editing Bharatpedia that allows people to contribute without having to learn wiki markup. This rich-text editor was made available as an opt-in release on the English-language Bharatpedia in December 2012, in 14 other languages in April 2013, and in most other languages at the beginning of June 2013. As of April 2015, it was available by default to users of about 76% of the language editions of Bharatpedias and as an opt-in beta feature to the rest, along with most non-Bharatpedia projects except Wiktionary and Wikisource. On English Bharatpedia, it is enabled by default for new users.

As of 2021, the visual editor is used about half as often as the 2010 wikitext editor, and about as often as the mobile web editor. It is used about twice as often as Twinkle.

To learn more about using VisualEditor, please read the guide to VisualEditor and the list of common keyboard shortcuts. Your help with the many tasks that need to be done is appreciated. You can also receive regular status updates on your talk page by signing up for the VisualEditor newsletter.

Limitations

Current known limitations include:

• Not available in talk or discussion namespaces – In the English Bharatpedia, VisualEditor is not enabled for any talk pages, in the Template or Bharatpedia namespaces, and in several of the namespaces that are rarely edited. The "Edit" button for VisualEditor is not available on pages where VisualEditor cannot be used. The Reply tool has a visual mode based on VisualEditor, as well as a wikitext mode with a live preview.
• Template parameters are wikitext, not rich text – VisualEditor lets you edit the parameters of template transclusions, but only as "wikitext" (so "[[Foo]]" or nested templates like "{{Foo|{{Bar}}}}", not "Foo" or "{{Foo|{{Bar}}}}").
• Incomplete editing functionality – The content of some complex formatting, including definition lists, will display and can be edited, but editors using VisualEditor cannot modify certain details. Multi-column lists are edited through the complex transclusion dialog, which is difficult. Table editing on Mobile doesn't work properly. Adding features in this area is one of the developers' priorities.
• Some browsers not supported – VisualEditor works in almost all relatively modern (2012 or newer) versions of Chrome/Chromium, Firefox, Edge, Internet Explorer, Safari, Opera, Midori, Falkon (formerly Qupzilla), SeaMonkey and WebPositive (approximately 95% of all users). VisualEditor will never work in some browsers that do not follow web standards, including Android 2.3 or Internet Explorer 10 or prior. If VisualEditor is not available in your browser, or if you have turned off Javascript, then you will see the buttons for the wikitext editor only.
• Footnotes inside templates – Footnotes inside templates (most commonly, infoboxes and {{reflist}}) are not visible in the "reuse" dialog, causing discrepancies in the numbering of footnotes displayed at the bottom of the main VisualEditor editing window.
• Numeric reference names – Currently, VE automatically adds numeric ref names with a colon prefix, i.e., ":0", ":1", ":2", and so on. There has long been interest in having VE support named references.
• Unbalanced templates – VisualEditor struggles with templates that pass a bit of incomplete code, with markup, to another template or table. These may display oddly or may not be editable if selected in VisualEditor.
• Slower – Loading longer pages into VisualEditor can take 60 seconds or more for some users.
• Cannot edit a single section – VisualEditor loads and submits only entire pages. Clicking an edit link for a section will scroll to the appropriate section upon opening. In VisualEditor's model, editing sections would be paradoxically slower than editing the whole page. [Note: Opening an entire page for editing does not increase edit conflicts, which are (roughly) based on editing the same paragraph.]
• Cannot upload non-free images – At this time, images that are uploaded inside either the wikitext editor or VisualEditor are sent directly to the Wikimedia Commons, which does not accept non-free images. All images that fall under Bharatpedia's non-free content policy must instead be stored on Bharatpedia using the File Upload Wizard. Commons also runs a filter to reject many images uploaded by editors who have not made many prior edits to Commons, especially for small or low-resolution images.
• Unaware of table formatting done by templates – Popular table cell templates (e.g. yes, no, tba, n/a) can cause issues. The reason is that these templates contain a pipe character to separate formatting and text, but VisualEditor isn't aware of this. As a result, table operations which change the table structure, such as merging/splitting cells or inserting/deleting/moving rows or columns, may not work properly.
• Data in merged cells is deleted if rows or columns are moved across them. Workaround: Unmerge the affected areas before moving, and merge them again afterwards.

You can click "Review your changes" to review the wikitext changes before saving a page. Please report any problems you see.

How to help out

Help is needed to make VisualEditor as good as it can be: You can find and report bugs and ideas for improvements or lend a hand in many other tasks, such as:

• Updating help pages – All Wikimedia Foundation projects have help pages to make contributing easier for new editors. Unfortunately, the full launch of VisualEditor will make obsolete the screenshots and tutorials in these help pages, because they describe how to edit using the markup editor. Therefore, the VisualEditor development team needs help updating help pages. The user guide to VisualEditor is a starting place for text for the new help pages.
• Adding TemplateData code to template documentation pages – VisualEditor features an interactive template editor—described in more detail in the user guide—and as you'll see if you use it on Bharatpedia, some templates display named parameters and nice descriptions that make the interactive template editor easy to use. However, other templates lack them, because they need TemplateData code added to their documentation pages for this feature to work. If you're interested in adding TemplateData, read the guide for it and a list of some of the most transcluded templates that may still need TemplateData added to their documentation.
• Help new users – Even though editing with VisualEditor may be easier, learning policies and guidelines and how to interact with the community is always challenging for new editors. You can help by spending time at the appropriate venues: the Help desk, the Teahouse, and the help chatroom. Additionally, please feel free to monitor the Category of Bharatpedians looking for help.

Userbox

Template:Userbox top User:Psiĥedelisto/Userboxes/VisualEditor User:Psiĥedelisto/Userboxes/VisualEditor User:Psiĥedelisto/Userboxes/VisualEditor Template:Userbox bottom You can signal to other editors your use of the VisualEditor on your userpage by using the userbox User:Psiĥedelisto/Userboxes/VisualEditor. See that page for all the options available.

External links

• The mediawiki.org page about VisualEditor, which links to historical regular status reports from 2011 through 2016.
• The mediawiki.org page about Parsoid, the bidirectional wiki parser behind VisualEditor, and historical regular status reports from 2011 through 2014.
• A 2015 study on VisualEditor's effect on newly registered editors

Subpage Index
VisualEditor/User guide