|Witajće do korčmy Wikipedije!
Tu je městno za wšitke prašenja k projektej, k wužiwanej software a podobnemu. Starše přinoški namakaš w archiwje.
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
Did you know that you can now use the visual diff tool on any page?
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 "Visuelle Unterschiede", 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.
Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.
- 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. 
- Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. 
- The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
2. měrca 2018, 21:56 (CET)
Wikipedia:Galicia 15 - 15 Challenge is a public writing competition which will improve improve and translate this list of 15 really important articles into as many languages as possible. Everybody can help in any language to collaborate on writing and/or translating articles related to Galicia. To participate you just need to sign up here. Thank you very much.--Breogan2008 (diskusija) 12. měrca 2018, 15:07 (CET)
Die WikiCon 2018 findet vom 5. bis 7. Oktober in St. Gallen in der Schweiz statt. --Holder (diskusija) 19. apryla 2018, 06:45 (CEST)
Time to bring embedded maps (‘mapframe’) to most Wikipedias[žórłowy tekst wobdźěłać]
Time to bring embedded maps (‘mapframe’) to most Wikipedias
Hilf bitte mit, in deine Sprache zu übersetzen
Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.
A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.
Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!
CKoerner (WMF) (talk) 24. apryla 2018, 23:38 (CEST)
From May 8, AdvancedSearch
will be available as a beta feature
in your wiki. The feature enhances the search page
through an advanced parameters form and aims to make existing search options
more visible and accessible for everyone. AdvancedSearch is a project by WMDE Technical Wishes
. Everyone is invited to test the feature and we hope that it will serve you well in your work!
Birgit Müller (WMDE) 7. meje 2018, 16:53 (CEST)
New Wikipedia Library Accounts Available Now (May 2018)[žórłowy tekst wobdźěłać]
The TWL OWL says sign up today!
The Wikipedia Library is announcing signups today for free, full-access, accounts to research and tools as part of our Publisher Donation Program. You can sign up for new accounts and research materials on the Library Card platform:
- Rock's Backpages – Music articles and interviews from the 1950s onwards - 50 accounts
- Invaluable – Database of more than 50 million auctions and over 500,000 artists - 15 accounts
- Termsoup – Translation tool
Many other partnerships with accounts available are listed on our partners page, including Baylor University Press, Loeb Classical Library, Cairn, Gale and Bloomsbury.
Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 30. meje 2018, 20:03 (CEST)
- You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
- This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.
Update on page issues on mobile web
Hilf bitte mit, in deine Sprache zu übersetzen
Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.
So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:
- The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
- Page issues make sense to readers and they understand how they work
- Readers care about page issues and consider them important
- Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues
Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.
CKoerner (WMF) (talk) 12. junija 2018, 22:58 (CEST)
10. julija 2018, 21:19 (CEST)
Consultation on the creation of a separate user group for editing sitewide CSS/JS[žórłowy tekst wobdźěłać]
(Hilf bitte mit, in deine Sprache zu übersetzen)
I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like
MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!
Tgr (talk) 12. julija 2018, 10:45 (CEST) (via global message delivery)
(Hilf bitte mit, in deine Sprache zu übersetzen)
To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like
MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.)
A new user group,
interface-admin, has been created.
Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with
.js that is either in the
MediaWiki: namespace or is another user's user subpage).
You can learn more about the motivation behind the change here.
Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats).
This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).
Tgr (talk) 30. julija 2018, 15:08 (CEST) (via global message delivery)
Enabling a helpful feature for Template editors[žórłowy tekst wobdźěłać]
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.
You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.
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 9th of August.
CKoerner (WMF) (talk) 6. awgusta 2018, 23:28 (CEST)