Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Insert" menu and click the "References list" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references.
Finally, click "Insert" in the dialog to insert the References list. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "Edit" and "Edit source" tabs into a single "Edit" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Editing" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[2] A similar feature will display the first part of hidden HTML comments.[3]

Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[4]

At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[5]

The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[6] In the future, the "Save page" button will say "Publish page". This will affect both the visual and wikitext editing systems. More information is available on Meta.

Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[7]

The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

Share your experience and feedback as a Wikimedian in this global survey[edit]

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future.[survey 1] The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. To say thank you for your time, we are giving away 20 Wikimedia T-shirts to randomly selected people who take the survey.[survey 2] The survey is available in various languages and will take between 20 and 40 minutes.

You can find more information about this project. This survey is hosted by a third-party service and governed by this privacy statement. Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email to surveys@wikimedia.org.

↑This survey is primarily meant to get feedback on the Wikimedia Foundation's current work, not long-term strategy.

↑Legal stuff: No purchase necessary. Must be the age of majority to participate. Sponsored by the Wikimedia Foundation located at 149 New Montgomery, San Francisco, CA, USA, 94105. Ends January 31, 2017. Void where prohibited. Click here for contest rules.

Dear Elitre, I am writing to inform you that you are in danger of losing your adminship on Commons because of inactivity.

If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section/Feb-Mar 2017 within 30 days of today's date, and also to make at least five further admin actions in the following six months. Anyone who does not do so will automatically lose administrator rights.

Your feedback matters: Final reminder to take the global Wikimedia survey[edit]

(Sorry to write in Engilsh)

Hello! This is a final reminder that the Wikimedia Foundation survey will close on 28 February, 2017 (23:59 UTC). The survey is available in various languages and will take between 20 and 40 minutes. Take the survey now.

If you already took the survey - thank you! We won't bother you again.

About this survey: You can find more information about this project here or you can read the frequently asked questions. This survey is hosted by a third-party service and governed by this privacy statement. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through EmailUser function to User:EGalvez (WMF) or surveys@wikimedia.org. About the Wikimedia Foundation: The Wikimedia Foundation supports you by working on the software and technology to keep the sites fast, secure, and accessible, as well as supports Wikimedia programs and initiatives to expand access and support free knowledge globally. Thank you! --EGalvez (WMF) (talk) 07:56, 24 February 2017 (UTC)

When you are finished editing the page, type your edit summary and then choose "Review your changes".

In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

Click the toggle button to switch between visual and wikitext diffs.

The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. You can read and help translate the user guide, which has more information about how to use the visual editor.

A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [8]

You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [10]

The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [11]

The Categories item has been moved to the top of the Page options menu (from clicking on the "hamburger" icon) for quicker access. [12] There is also now a "Templates used on this page" feature there. [13]

You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [14]

The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [16]

A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [17]

There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K or Command+K respectively. [18]

The team is working on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [19]

The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [20]

If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

Hello Elitre, we are aware that using the old installation method of VFC (via common.js, which you are using) may not work reliably anymore and can break other scripts as well. A detailed explanation can be found here. Important: To prevent problems please remove the old VFC installation code from your common.js and instead enable the VFC gadget in your preferences. Thanks! --VFC devs (q) 16:23, 22 May 2017 (UTC)

I'm writing you as one of the most active Commons users right now. Since a while now, the idea of a dedicated Commons conference has been floating around. But since the last Wikimania concrete steps have been taken to actually make it happen next year.
If you're interested in participation or maybe willing to help organize the first ever Commons Conference, I invite you to check out the project page and leave your comments; or just show your support for the idea, by signing up.

A file that you have uploaded to Wikimedia Commons, File:Next Stop, Axum, Ethiopia (2809170679).jpg, is a derivative work, containing an "image within an image". Examples of such works would include a photograph of a sculpture, a scan of a magazine cover, or a map that has been altered from the original. In each of these cases, the rights of the creator of the original must be considered, as well as those of the creator of the derivative work.

While the description page states who made this derivative work, it currently doesn't specify who created the original work, so the overall copyright status is unclear. If you did not create the original work depicted in this image, you will need to specify the owner of the copyright.

Please edit the file description and add the missing information, or the file may be deleted. If you created the original content yourself, enter this information as the source. If someone else created the content, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so. Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you!

Dear Elitre. I am writing to inform you that you are in danger of losing your adminship on Commons because of inactivity.

If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section within 30 days of today's date, and also to make at least five further admin actions in the following six months. Anyone who does not do so will automatically lose administrator rights.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!