Help:VisualEditor/VE as Beta Feature

Here is a quick-start guide so that you can learn how to support your community while VisualEditor is a Beta Feature for logged-in users at your wiki.


 * 1) The first step is involving your whole community to let them know VisualEditor is now available in Beta Features and to get further help with the following tasks.  Tip: you can link to this page from your Village Pump, you can set up a sitenotice, or a watchlist notice for logged-in contributors.
 * 2) There is key documentation to translate, mainly the User guide and the interface itself.  Tip: for more information and instructions, please see VisualEditor/TranslationCentral.
 * 3) Help:TemplateData contains information about how to add TemplateData information to common templates on your wiki.  This is important because if templates do not include this data, they will be difficult to use inside VisualEditor.  There is now an editing tool that allows you to add TemplateData in a simpler way.  Start with templates that are often used in articles, such as citation/reference templates and infobox templates.  The Special:MostTranscludedPages special page on your wiki might help you find out which are the most important templates you need to work on.  The ones which are heavily used in the article namespace have the priority.  Tip: check how other wikis did this.  For example, here is the TemplateData for the    template at the English Wikipedia.  If you recently imported    from that wiki and didn't customize it further, then copy/pasting their TemplateData will probably work for you.
 * 4) Check bugs on the local feedback page, if your wiki has one, to see if they are already known to developers in this list.  Tip: follow the steps provided here.  When Bugzilla gets closed, you'll need to report bugs at Phabricator instead.  You can also report problems by leaving a message at the central feedback page.
 * 5) Patrollers might want to keep an eye on the log of edits made with VisualEditor for a few weeks.  You can reach it from this link (you'll need to change language code and sister project name in the browser's address bar after you click on it).  Tip: the highest chance to make mistakes with VisualEditor will actually come from experienced users, who'll just need some time to adapt to the new environment.
 * Please let the VisualEditor team know if you have further questions. Click here to go to the main VisualEditor page.