Kartographer improvements on the Wikimedia wishlist[עריכה]
The kartographer is one of our most important features. RolandUnger has proposed some urgently needed improvements. If you want to support these wishes please vote on meta wiki for the Kartographer improvements. I wish you a very merry Christmas. Thank you very much.
We propose an edit-a-thon dedicated to the 5th anniversary of the Wikivoyage launch at the WMF servers that took place on January 15, 2013. At Russian Wikivoyage it will be combined with the celebration of our 5000th article that we expect in early January. In a nutshell, we plan to request central banner on relevant language versions of Wikipedia, and offer small presents to everyone who makes useful edits to Wikivoyage articles during the period of January 16 - February 15, 2018.
We prepared several pages:
Landing page that explains the basics of adding new objects and editing the existing ones; how to use Listing Editor and what to write in the description field
Getting started, where we explain how to use Wikivoyage (dynamic maps, images, GPX files, offline usage) and what is special about our project; how we are different from other travel guides
Rules of the edit-a-thon. The participants will score 1 point for each object added to an article, provided that they add practical information and write a meaningful description based on their first-hand knowledge. Copying information from the web is strongly discouraged.
Every participant who scored more than 10 points, will receive postcards (this is equivalent to the prizes given for the Asian Month in Wikipedia). Those participants who will write at least 2 articles with the usable or guide status will receive printed travel guide for the region of their choice.
These are the rules at Russian Wikivoyage. You should feel free to modify them in your own way, but please, stick to several general guidelines:
Prepare the landing page that will include brief instructions on which articles to edit, how to edit them, as well as links to relevant policies and guidelines in your language
Provide the text of the central notice in your language
Name one person who will be responsible for the communication
If you plan to give presents, draft formal rules and find the presents. Our presents are partly funded by Wikimedia Russia and partly by ourselves. Talking to your regional chapter or even writing a rapid grant application may be a good idea. The prizes are not compulsory, but they are likely to increase the number of participants and motivate them to work harder.
Deadline: January 4, 2018. After this date I will initiate the Central Notice request on meta. Without the landing page and other relevant information, I won't be able to include your language into the request, and you won't have the central banner. Should you have question, please, ask them here or on my talk page. Happy New Year, and all the best in 2018!
Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.
If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.
Click the toggle button to switch between visual and wikitext diffs.
In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.
You can read and help translate the user guide, which has more information about how to use the visual editor.
The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. 
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. We will notify you when the next issue is ready for translation. תודה!
The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.
TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.
TemplateStyles is useful for a few reasons.
It makes it possible for templates to work better on mobile.
It cuts out confusion on where to apply CSS rules.
Editing CSS is currently limited to administrators, which is a major barrier to participation.
All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.
This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 28th of March.