Meta:Babel
- You can comment here in any language.
- This forum is primarily for discussion of Meta policies and guidelines, and other matters that affect more than one page of the wiki.
- If your comment only relates to a single page, please post it on the corresponding discussion page (if necessary, you can provide a link and short description here).
- For notices and discussions related to multilingualism and translation, see Meta:Babylon and its discussion page.
- For information about how to indicate your language abilities on your user page ("Babel templates"), see User language.
- To discuss Wikimedia in general, please use the Wikimedia Forum.
- Consider whether your question or comment would be better addressed at one of the major Wikimedia "content projects" instead of here.
 |
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.
|
The Vector 2022 skin as the default in two weeks?[edit]
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.
- Top of an article
-
Vector legacy (current default) -
Vector 2022
- A section of an article
-
Vector legacy (current default) -
Vector 2022
About the skin[edit]
[Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.
[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.
Our plan[edit]
If no large concerns are raised, we plan on deploying on 31 October. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. We will gladly answer! Also, check out our FAQ. Thank you! SGrabarczuk (WMF) (talk) 00:25, 19 October 2023 (UTC)
- As I have written on Phabricator, this is no place for configuration change proposals. You need to roll back the deployment and start a proper RFC with the community such as it was for example done for Meta:Requests_for_comment/Adding a local rollbacker flag or alternatives. Acting in such a way is disgusting disregard of community processes and is reminiscent of the superprotected thing. Base (talk) 00:05, 1 November 2023 (UTC)
- Courtesy link: phab:T349549 –Novem Linguae (talk) 01:08, 1 November 2023 (UTC)
- Anyone who doesn’t like the new skin can opt-out, which makes it different to configuration changes like the introduction of new user groups or superprotect.
- I don’t think technical changes like this - which are intended to offer a coherent user experience across all wikis - need special community approval. Johannnes89 (talk) 06:31, 2 November 2023 (UTC)
- Courtesy link: phab:T349549 –Novem Linguae (talk) 01:08, 1 November 2023 (UTC)
Comment per Base, that is not the way nor the timeframe to implement the change and for all users in all forms. This is not the web team's wiki, it is the community's and change occurs by our consensus. If you want to move people over then there are other ways to put that out as a proposal and enhance migration. — billinghurst sDrewth 03:55, 1 November 2023 (UTC)
Vector 2022 post-deployment conversation[edit]
Hey everyone! We have now completed the deployment of the Vector 2022 skin here on Meta-Wiki and wanted to begin a conversation about your experience with the skin so far. Have you encountered any issues with the skin itself or your gadgets and user scripts? Do you have any questions on new functionality? Are there any suggestions for further improvements?
We also heard from a fellow Meta-Wiki user that our initial messaging around deployment was perhaps not as visible as we had hoped. If you were unable to see our previous notice - we apologize! We will cross-post the link to this conversation across a few pages here on Meta-Wiki with the hope that we can get it in front of as many people from the community as possible.
Thank you! OVasileva (WMF) (talk) 06:42, 2 November 2023 (UTC)
- @OVasileva (WMF): I have moved the section as there is already some comment about the process that Web team undertook. Summary, your consultation process sucked. I was away for two weeks and had zero chance to comment. What was the hurry? Why couldn't you go through proper consultation, and seek some sort of consensus?
Personally I am not a fan, and immediately went back. <shrug> Most of the reason that I returned was that this skin obliterates my use of the gadget w:ru:MediaWiki:WEF_AllEditors.js which is an essential for me. I didn't try experimenting further. I didn't even bother trying to see what it was like on my laptop where I already don't like scrunched widths as I already do that myself, I typically never run a browser or any app in full screen. — billinghurst sDrewth 06:35, 3 November 2023 (UTC)
- Billinghurst, honestly, I don't see why two weeks is an improper consultation timeframe for Meta, as a smaller, non-content project that is editor and not reader-facing. — Frostly (talk) 20:42, 4 November 2023 (UTC)
- @Frostly: Zeroly, you are entitled to your opinion, as I am mine, so please be more thoughtful in a response. Firstly some of us take two weeks holiday, and in this case it completely aligned with my ability to comment. Secondly, it was a universal and forced change, rather than using other available processes, with an ugly twist in the tail to revert. Thirdly, your explanation of metawiki could be used in exactly the opposite point of view about why it is unnecessary to force a change to logged in user accounts ... as a grown-up, I don't need the WMF to force such choices of the skin upon me nor change what I have set.
Happy for people to be invited to move to the new skin, put up links to make it easy for them to do so. Happy for it to be the new default for new accounts. All very reasonable,. What is not reasonable is for me to come back to editing and have to bloody well work out someone has force changed my settings and for me to have to unbreak things to get things working when I just want to get my tasks done. Whether it is loved, or not loved, is irrespective of the process, and the outcome. — billinghurst sDrewth 00:03, 5 November 2023 (UTC)
- Billinghurst, my apologies for the brevity. This page might be helpful to reference. In particular, I think that in this case, the research...performed beforehand would be summarized in these reports. Best, — Frostly (talk) 03:16, 8 November 2023 (UTC)
- @Frostly: Zeroly, you are entitled to your opinion, as I am mine, so please be more thoughtful in a response. Firstly some of us take two weeks holiday, and in this case it completely aligned with my ability to comment. Secondly, it was a universal and forced change, rather than using other available processes, with an ugly twist in the tail to revert. Thirdly, your explanation of metawiki could be used in exactly the opposite point of view about why it is unnecessary to force a change to logged in user accounts ... as a grown-up, I don't need the WMF to force such choices of the skin upon me nor change what I have set.
- Billinghurst, honestly, I don't see why two weeks is an improper consultation timeframe for Meta, as a smaller, non-content project that is editor and not reader-facing. — Frostly (talk) 20:42, 4 November 2023 (UTC)
- I love it! — Frostly (talk) 20:40, 4 November 2023 (UTC)
- Hello.Sorry write japanese and I'm read google translate.
- デフォルトとして展開するには、準備不足であると言わざるを得ません。
- 目次はプロジェクトのフッターを隠しています。全言語版で確認しているわけではありませんが、Wikipedia ではこの不具合（？）はないようなので、mediawiki には対応するモジュール（？）か何かがあると思います。
- 重ねて言いますが、既定の skin にするには準備が不足していました。 温厚知新 (talk) 09:30, 30 November 2023 (UTC)
Please sync above page with CNBanner:Wm2023scholarcfp 2-text1/sr
Regards Milicevic01 (talk) 00:03, 18 November 2023 (UTC)
- @SGrabarczuk (WMF): Can you please update message with new translation --Milicevic01 (talk) 13:04, 19 November 2023 (UTC)
- Done, @Milicevic01. Thanks for reminding me to check out the latest translations :) SGrabarczuk (WMF) (talk) 14:59, 20 November 2023 (UTC)
Ready for translation: Education Newsletter November 2023[edit]
November 2023 education newsletter released for translation. Please help our readers to read education newsletter in their native language. The latest education newsletter is ready for translation: here Newsletter headlines link for translation: here (please translate by December 13, 2023) Individual articles for translation: Category:Education/Newsletter/November 2023. Regards, ZI Jony (Talk) 14:26, 11 December 2023 (UTC)