Help:VisualEditor/VE as the main editor/fa

Here is a quick-start guide so that you can learn how to support your community while VisualEditor becomes available by default to editors at your wiki.

چگونه یک وظیفه ثبت شود. You can also report problems by leaving a message at the central feedback page on this site.
 * 1) The first step is involving your whole community to let them know VisualEditor is now available for editors at your wiki and to get further help with the following tasks.
 * 2) * You can start a conversation at your Village Pump in your language and then link to this page, or you can set up a sitenotice, or a watchlist notice for logged-in contributors.
 * 3) * Make sure that local documentation, especially pages read by new editors such as tutorials for newcomers, editing guides etc., mentions VisualEditor and its documentation. You may want to provide a dedicated space (a sandbox in the main or in the User: namespace) where even logged-out editors can try VE. Here is an example of how this was done on the English Wikipedia (note the ?veaction=edit string at the end of the URL).
 * 4) There is key documentation to translate, mainly the User guide and the interface itself.
 * 5) * Tip: For more information and instructions, please see VisualEditor/TranslationCentral.
 * 6) 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.
 * 7) * Tip: There is now an editing tool that allows you to add TemplateData in a simpler way.
 * 8) * Start with templates that are often used in articles, such as citation and reference templates, as well as infoboxes. The 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.
 * 9) * 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 copying and pasting their TemplateData will probably work for you.
 * 10) Check bugs on the local feedback page, if your wiki has one, to see if they are already known to developers.
 * 11) *  Reporting bugs or feature requests directly on Phabricator will catch the developers' attention more quickly. A mention of the report and any updates to it will also appear live in the #mediawiki-visualeditor IRC channel.
 * 1) 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!).
 * 2) * Tip: Experienced users may make more mistakes than expected, as they need some time to adapt to the new environment.
 * 3) Add special characters which are relevant to your language to the set of characters displayed inside the related tool.
 * 4) *Tip: See the instructions page at mediawiki.org to learn more about this.
 * 5) Set up a customized Cite menu with the most used Cite templates at your wiki.
 * 6) *Tip: See the instructions page at mediawiki.org to learn more about this.
 * 7) Keep yourself and your community up-to-date on VisualEditor news.
 * 8) *Tip: Sign up for the multilingual monthly newsletter, and please add your name to the translators' list so that other people at your wiki will be able to read the bulletin in your language on community pages there.

اگر مطالبی می‌دانید که به پیشرفت این ابزار کمک می‌کند، لطفاً تیم توسعه‌دهندهٔ ویرایشگر دیداری را آگاه کنید. اگر مطالبی می‌دانید که به پیشرفت این ابزار کمک می‌کند، لطفاً تیم توسعه‌دهندهٔ ویرایشگر دیداری را آگاه کنید.