Wikipedija:Portal
- dsb [update needed per en]: Pšośby za chórogój bota pšosym pisaś na toś tom boku. Wót casa, až toś ta wikpedija njama bureaucrata, pśizwólenje za pśistup buźo źěłane pśez stewarda kak njebuźo how protestow. Standardna politika za botow jo wužywana na tos tej wiki, z awtomatiskem pśigłosenjem za typy botow, kótarež su pśizwólone.
- en: Requests for the bot flag should be made on this page. This wiki uses the standard bot policy, and allows global bots and automatic approval of certain types of bots. Other bots should apply below, and then request access from a steward if there is no objection.
Wopśimjeśe
| Archiwy |
Editing News #1—2018[žrědłowy tekst wobźěłaś]
Read this in another language • Subscription list for this multilingual newsletter
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.
Recent changes[žrědłowy tekst wobźěłaś]
- 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. [1]
- Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [2]
- 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.
Let's work together[žrědłowy tekst wobźěłaś]
- The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
- Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
- The
<references />block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [3] - 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. Wulki dźak!
2. měrca 2018, 21:56 (CET)
Galicia 15 - 15 Challenge[žrědłowy tekst wobźěłaś]
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, 14:55 (CET)
Welcome to Wales! The Celtic Knot Conference...[žrědłowy tekst wobźěłaś]
I apologise that this invitation is in English; feel free to translate into your own language!
I would like to invite you to the second Wikipedia language conference focusing on supporting Celtic and other small and Indigenous Languages. This year 'Celtic Knot' will be at held on the 5th and 6th of July at the National Library of Wales in Wales' most famous seaside resort of Aberystwyth.
For more information on how you could be part of this great event, pop over to our website where you can also contact Jason Evans, our National Wikimedian and conference organiser. We have many speakers who will talk about what works for them, how we can learn from each other... small is beautiful...
Viva la diversity! Llywelyn2000 (diskusija) 4. apryla 2018, 14:57 (CEST)
WikiCon 2018[žrědłowy tekst wobźěłaś]
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ědłowy tekst wobźěł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)
Update on page issues on mobile web[žrědłowy tekst wobźěłaś]
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)
Enabling a helpful feature for Template editors[žrědłowy tekst wobźěłaś]
Hello.
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.
Thank you.
CKoerner (WMF) (talk) 6. awgusta 2018, 23:28 (CEST)
Editing News #2—2018[žrědłowy tekst wobźěłaś]
Read this in another language • Subscription list for this multilingual newsletter
Did you know?
Did you know that you can use the visual editor on a mobile device?
Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.
You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.
Remember to publish your changes when you're done.
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 wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.
Recent changes[žrědłowy tekst wobźěłaś]
- The Editing team has published an initial report about mobile editing.
- The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
- The Reading team is working on a separate mobile-based contributions project.
- The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar. You may choose another editing tool in your editing preferences, local gadgets, or beta features.
- The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
- The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published. [4]
Let's work together[žrědłowy tekst wobźěłaś]
- The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
- The Community Wishlist Survey begins next week.
- 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. Wulki dźak!
2. nowembra 2018, 15:17 (CET)