Talk:Reading/Web/Desktop Improvements

Vector 2022 is just awesome, but I have some recommendations

 * Thank you very much for this new design!
 * It is clearly arranged and flexible, I really love it!
 * Here are my recommendations:
 * The buttons for "Your alerts" and "Your notices" should be in that bar too, that pops up, when you scroll down. At least in that user menu.
 * There should be an opt-in for having all the subentries in the table of content (toc) fold out by default.
 * Also I noticed, that when you hover the mouse in the toc and scroll to the top or the bottom of it, it will begin to scroll the text on the right (article for example) and the toc will reset to the position that matches the position in the text. That is really annoying.
 * Best Regards --KleinerKorrektor (talk) 19:21, 18 February 2023 (UTC)
 * Hello @KleinerKorrektor. Thank you for your ideas. I've documented your request to add the icons in the sticky header, as we call it. We're also figuring out how to build this functionality to force all the headings to be shown. Regarding the third issue, are you still experiencing this? I'm not sure what you'd expect instead. Sorry, perhaps I just don't quite understand what you mean. Thanks! SGrabarczuk (WMF) (talk) 17:57, 30 March 2023 (UTC)

Limit the screen width
I think the worst one can do is limit the screen width... I's far less relaxed for reading and a waste of screen space. Switched back to the previous version. 213.219.163.24 23:41, 21 March 2023 (UTC)
 * Hello! I'd like to invite you to read this page: Reading/Web/Desktop Improvements/Features/Limiting content width. There we've documented our arguments for this change. If you prefer the full width, you may use the button in the bottom right corner of the screen, too. I hope this solves the issue! SGrabarczuk (WMF) (talk) 17:57, 30 March 2023 (UTC)
 * I have a somewhat related question. I see that there is a toggle on the MediWiki site in the bottom right corner to adjust width, which is great... but I don't see it on my own install using Vector 2022 (MediaWiki version 1.39.3). Is there something I'm missing in order to make that visible? I don't have the "Enable limited width mode" option in user preferences either. Thanks in advance for any insight you can offer. Adoxtater (talk) 02:29, 27 April 2023 (UTC)

The new layout looks horrible
No offence, but I created an account just because the new format is badly designed.

Hello,

I study education and am in deep shock about the new wikipedia layout. Why the fuck do UI designers think removing borders and cramping everything into togglers actually makes things better? Like who the fuck sparked that trend? Apple?

What used to look like an encyclopaedia now looks like a white wall of simply nothing. There no longer seems to be any visual (like actually visuable) organization of a page beyond the paragraphs.

It isn't just that there aren't any visible borders anymore, there also is no contrast whatsoever and the text flickers while scrolling! It horrid and counterintuitive as fuck, because it makes your eye get lost and is utterly immemorable and thus fails to fulfill the basic criteria of visual educational material.

Get education experts when designing the UI next time. This is shameful.--2A02:908:966:63E0:E94E:DAB1:D3A:483 12:55, 21 January 2023 (UTC)


 * I totally agree with your comment! I have no idea how someone may break so much the user experience as they did. I haven't been logged to wikipedia for more than a decade, but had to, to choose some older variant of visual style, to even usefully read an article. A shame on them, a shame! How come they have not tested it before release. Sslukt (talk) 15:11, 21 January 2023 (UTC)
 * Small correction, they did test it before release (and I hated it then too), but couldn't figure out how to put it into words. The OP states it excellently. Wiki joedirt (talk) 23:16, 30 January 2023 (UTC)
 * Same! I haven't logged in for 7 years, but now had to, just to change the layout.. why do you even need to log in for that? makes no sense. P3rttiz (talk) 14:30, 17 February 2023 (UTC)
 * I agree, but it's not just here. The entire Web seems to be going through a phase of ugly and stark being considered design statements. I do hope it passes quickly. 74.115.78.80 15:28, 21 January 2023 (UTC)
 * Absolutely agree. All the illustrations have been reduced to postage stamps. It looks fine on a phone, but is utterly unusable on a computer screen. The aesthetics have been trashed along with the functionality. The web is a visual experience and Wikipedia has just died... 2001:8003:D40E:7E00:ACDF:D45C:10E0:7BF4 17:06, 21 January 2023 (UTC)
 * Agree. Some websites tend to change themselves radically (e.h. IMDb) when old version is working just fine. Gevorg89 (talk) 17:29, 21 January 2023 (UTC)
 * I agree, the new-look looks extremely unorganized, but at least you can switch back to the old one... Telltemmne (talk) 18:54, 21 January 2023 (UTC)
 * Certainly, the new layout looks utterly dreadful, good thing we can change back to either vector legacy or monobook. Interlacing (talk) 20:02, 21 January 2023 (UTC)
 * Agree. Clear-cut downgrade. Forresthopkinsa (talk) 21:12, 21 January 2023 (UTC)
 * I've been using Wikipedia since day 1 and I had to create my first account today just so I can change the layout to the old format. What a HORRIBLE redesign.  It's looks like garbage on a widescreen laptop monitor.  Why is there so much white space on the left side?  Is wikipedia for Zoomers on iPhones now, like TikTok or some other garbage?  This is the worst website redesign I've ever seen, including that one that Digg did like 12 years ago that made literally everyone leave the site for Reddit.  Just BAD BAD BAD. 76.104.139.237 21:31, 21 January 2023 (UTC)
 * so fucking true man 71.226.203.33 23:41, 30 January 2023 (UTC)
 * It is nothing but worse. Jacob Agar (talk) 21:33, 21 January 2023 (UTC)
 * I actually came here to say the same thing; the new UI isn't just ugly, but it's genuinely painful to use on desktop, to the point of being borderline-unusable. It was clearly designed with mobile users in mind, despite the fact that, afaik, the overwhelming majority of editors prefer desktop; I say this as someone who does mobile edits from time to time. I don't want to have to log in every time I use Wikipedia just so I can even navigate a page! Change it back! Birdn4t0r (talk) 22:02, 21 January 2023 (UTC)
 * You can get the mobile UI on desktop already with .m in the url. I just switched from the mobile view that had opened up by accident to desktop view and I think the layout is even worse on desktop than the actual Mobile UI. This style is not ready for prime time and should in no way have become the default.
 * The UI getting old and stale is worse than being actively bad.
 * Shadowmaster13 (talk) 08:26, 25 January 2023 (UTC)
 * Count me in on that one: Huge waste of screen real estate, on my 1920 pixel width screen only half is used by content and it would not be more if resize the browser window to full screen. The article-outline was separated from the article, no visible connection between article and pictures/graphics, way too light UI overall, languag switcher anywhere and search-field moved anywhere else.
 * Seems like it was designed to fuck up and bug out the user. No real user experience while designing this was in mind i think. 2A02:8109:9D40:1F1C:E475:3EC8:7B5E:28CE 23:34, 21 January 2023 (UTC)
 * I made an account with wikipedia just to switch it back. It's not so much the design is horrible, but it looks exactly like the mobile layout and I don't use the mobile layout for a reason. I don't entirely unsupport the idea of re-optimizing Wikipedia for modern UI (not that I wouldn't switch it back anyways lol) but doing it in a way that just feels like copying the mobile format is so weird. 47.146.190.208 02:16, 22 January 2023 (UTC)
 * While I disapprove of the profane language used in this comment, I have to echo the sentiment. The amount of white space in the new layout is so jarring it makes articles absolutely dreadful to read on a desktop display. Does Wikipedia even care about how resoundingly negative the feedback to this new design has been? 2600:6C44:747F:98D5:E9C9:BDC3:1868:6F99 03:30, 22 January 2023 (UTC)
 * Uninspired redesign, neither better looking or more functional, so I have no idea what was the intention of whoever came up with this. There is no way someone beta tested this because it would not have gone live.
 * I have no idea why someone thought the interface needs a change in the first place since it was optimized for a dictionary, but on top of that, it made no sense to take away the access to international versions and Wikimedia on the side which represent additional references. It would make more sense to make the old one default and offer the new one as option. 2600:1700:20C1:4920:B8D9:705C:D86C:BF8F 04:31, 22 January 2023 (UTC)
 * I'm mostly reply just to increase the number of replies so they see we don't like this; while the profanity is unnecessary I wholeheartedly agree that desktop websites should have desktop layouts and mobile layouts should stay on mobile. The same complaints were made when Windows 8 came out and when Facebook did it I stopped browsing their website on desktop entirely.  At the very least you can change it back in the preferences menu (although that's only available to those of us who've made accounts), unlike Facebook and the new Steam Library (which is not that new anymore). Jacob p12 (talk) 05:49, 22 January 2023 (UTC)
 * Completely agree. Vector 2022 sucks due to clearly very little thought being put into it. Excelsiorsbanjo (talk) 05:51, 22 January 2023 (UTC)
 * I literally went to the step of creating an account just so I could complain about (and hopefully get rid of) the horrific new UI. I've seen better web design in simple html pages from the 90s. --118.149.76.228 10:27, 22 January 2023 (UTC)
 * My main issue with it was that the text was not wide enough and it was harder to read. Glad there's a button at the bottom to make the width fluid. 5.15.71.147 12:06, 22 January 2023 (UTC)
 * This mostly fixed it for me, thanks for that!
 * While I'm here, my suggestion is for a border to be added to the edges of the container. The white blends into the grey too easily and it is a bit disorientating. The border helps the user find the edge of the page/container, and it also has the benefit of looking more authoritative. Moissanite (talk) 19:59, 8 February 2023 (UTC)
 * You're totally right. I also had to make an account to select the proper UI. This is clearly some change pushed by some kid who thinks JavaScript frameworks are the best just because some marketing move told him so. Maybe some company author of the framework donated money to Wikipedia to make this change. Otherwise it makes no sense and it just makes Wikipedia worse. Microph123 (talk) 12:45, 22 January 2023 (UTC)
 * Maybe the real purpose of the change was to get us all to make accounts.... 66.214.69.101 01:46, 26 January 2023 (UTC)
 * Thıs is absolutely true, there was no need for a resign as the older one was perfectly fine and the blank white space in the sides is horrid and a waste of space. Klad 2 (talk) 13:28, 22 January 2023 (UTC)
 * The new layout sucks so bad. While I think that the old layout looked kinda ugly, I definitely prefer the old one, because it's much easier to read with the old layout. Old is gold, especially on Wikipedia 109.247.106.208 13:45, 22 January 2023 (UTC)
 * I think maybe if they added a dark mode it wouldn't suck as much though. 109.247.106.208 13:47, 22 January 2023 (UTC)
 * At least it helped for user count, I had to create an account to revert to the old appearance. 2A02:AA13:7200:8A80:B8E5:F3A9:623C:352D 17:54, 22 January 2023 (UTC)
 * Can't agree more. I don't know if it was their intention to confuse people at first, and then force them to make an account to switch back from the horrible redesign, a la Reddit style. Terrible decision. 62.167.140.205 18:40, 22 January 2023 (UTC)
 * this is what i came here to say! the only reason i created my user account is so i could revert to the old design! the new one makes me want to vomit. Jakeyounglol (talk) 23:31, 22 January 2023 (UTC)
 * I can only agree. The new design is pretty much a compilation of every awful UI design from the past decade.  It's genuinely awful and makes the experience actively worse.  It really, really, really needs to be rolled back.  And I'm hoping WMF isn't going to dig in their heels about this.  Because the old design is flat out superior. 2600:1700:1471:2550:2195:BD59:6E8E:AB0C 01:29, 23 January 2023 (UTC)
 * Couldn't agree more, the new look is atrocious and an unbelievable waste of space. This is a perfect example of attempting to fix something that isn't broken. ElaenaS (talk) 01:47, 23 January 2023 (UTC)
 * I've been trying to give Vector 2022 a chance over the last few days, and what I really don't like so far is how dead it feels. Like, this lack of visible page organization, as you pointed out, makes it very dull. All this white without much contrast actually makes my eyes uneasy. That is my experience so far. RoadTrain (talk) 02:37, 23 January 2023 (UTC)
 * I too am chiming in to say I made an account for the first time in 30 years of using wikipedia to revert to the old format. The new vector is atrocious to look at and makes reading a chore. The old layout was engaging and helped you intake information. Thats part of the reason people could get lost in wikipedia it was so easy to read. 2603:8080:A704:5A81:A800:FCEE:7F61:1D8F 10:19, 23 January 2023 (UTC)
 * I created an account just to voice my distaste for the new layout. WHY is the width limited??? I get that to some it may be easier to read, but for me, with a 27" screen, I now have to scroll quite bit to read the same content. I MUCH rather read longer lines than be forced to scroll every couple seconds.
 * The previous design was clean and compact. Some may say cluttered, but really everything was at your fingertips and super convenient.. Like an airplane. The new design hides things behind annoying menus, and the TOC being hid behind toggles is REALLY DUMB. Now I can't see the outline of a page without guessing and randomly clicking on toggles?? WTF?! The new design also wastes ~2/3rds of horizontal space on a 27" monitor which looks really goofy. It feels so sterile, and like a clone of other wastelands of the modern web. Ugh. Frustrating. At least with an account, now I can revert the look. Jammnrose (talk) 17:56, 23 January 2023 (UTC)
 * Adding my voice to those who had to create an account just to go back to the old layout. The new one is just awful. Hargan2 (talk) 22:48, 23 January 2023 (UTC)
 * Ive always donated to wiki since i graduated college. I will never give them a cent ever again. Same thing with mozilla and mdn. Its like they used the same brain dead designer Randt1234 (talk) 23:39, 23 January 2023 (UTC)
 * I don't normally comment on talk pages, but good god is this new UI design the most useless one I've ever seen. Nobody asked you to hide everything behind unintuitive buttons, it was working just fine before you fiddled with it. Hobtan (talk) 23:49, 23 January 2023 (UTC)
 * Have to agree that this new redesign looks very bad. Please revert it!! 83.254.212.105 23:53, 23 January 2023 (UTC)
 * This is garbage.. I can't resize the content in a widescreen monitor to get full viewing width. Who thinks this is actually more usable ? Psiberfunk (talk) 03:21, 24 January 2023 (UTC)
 * I'm chiming in as a UX designer–this is shameful and I'm so very tired of "new" UI improvements just turning out to be hiding functionality behind toggle screens. Enuui (talk) 06:11, 24 January 2023 (UTC)
 * I've used the new layout for two weeks. I'm switching back to the old look because it displays the article in a wider column for reading and editing, because it doesn't have a right-nav bar for Tools that I have to hide, and because it uses gray backgrounds to guide my eyes. PRRfan (talk) 16:52, 24 January 2023 (UTC)
 * Couldn't agree more. HATE the new layout. There is so much white space it almost makes me sick. I don't know how web developers get the idea that they know better than I do about what size I want my window to be. I set it to a given size, some smart a**e developer sets 5" borders other content! How arrogant is that. If I wanted it that size I could easily do so. Guess what, I didn't. IanKennedy1965 (talk) 17:08, 24 January 2023 (UTC)
 * Agreed. New format is harder to navigate, particularly on the desktop. Many articles are actively more difficult to read, between the increased white space on the page and the way the text boxes have been 'streamlined'. Not sure if anyone in authority at Wikipedia is reading these comments, but you really dropped the ball on this redesign. 128.164.30.116 19:01, 24 January 2023 (UTC)
 * If I want to read on my phone, I grab my phone. Why do developers everywhere think that a desktop website should look like a phone website. This new appearance may disappear.
 * Why must everything always be hidden for an empty appearance?
 * More search and click work for the same result. Like logging in. To create an account one click. To log in two clicks. Willem ter Haar (talk) 21:12, 24 January 2023 (UTC)
 * The new UI looks awful. It's so bad it made me come here to let my voice be heard. Please change it back to the previous version while you come up with something better ☹ 71.208.54.176 22:56, 24 January 2023 (UTC)
 * Like many, I have created an account to switch back to the old style. Maybe this was the idea? The new design is woeful. What's the point of having a large monitor if you put all the text in a ribbon down the middle, with huge amounts of white space on each side. Horrible. 81.107.32.77 23:16, 24 January 2023 (UTC)
 * I agree. I thought the site was broken at first, then came to find out that this was done on purpose.
 * If nothing else, it pushed me to figure out how discussion pages work. But I'm deeply not in favor.
 * I'm not sure where all of the content on the left side of the page went. Is there a migration tutorial? 2600:1700:EB0:3790:D07F:D785:80DD:AC07 01:28, 25 January 2023 (UTC)
 * I thought i was on the mobile version then found out this was actually a new layout. This is just all around dumb. DarmaniLink (talk) 08:56, 25 January 2023 (UTC)
 * I will stop donations immediately if this is NOT changed back to default. The new "theme" is total shit and I will have NONE of it. This is not the reason I donate money to Wikipedia. Whoever made this decision should have been ousted yesterday. Revert it back to the previous DEFAULT and MAKE people choose the crappy 2022 (genX-edition) if they feel compelled. Newlayoutsucksass (talk) 10:58, 25 January 2023 (UTC)
 * I agree. As one may guess, I made an account just to be able too change the look. Please don't make non registered users suffer, they're people too! WikiP&#39;sNew2023UIisTRASH (talk) 20:20, 25 January 2023 (UTC)
 * While you’re welcome to voice your opinions/feedback about wiki functions, please do not take it into account usernames. Tropicalkitty (talk) 20:33, 25 January 2023 (UTC)
 * Had to make an account just to go back to the old design where the content isn't squished into a tiny section just to make room for whitespace 108.31.241.8 20:26, 25 January 2023 (UTC)
 * I completely agree!! I thought that the CSS template was not loading properly to start with, then that facepalm moment.
 * I am surprised because they think MOBILE MODE is a must, that there wasn't a forced DARK MODE as well.
 * Even the Skin Appearance Preferences does NOT SAVE EITHER, Seriously WTF Shealladh (talk) 10:47, 26 January 2023 (UTC)
 * totally agree, horrible UI, but fortunately you can change it in preferences, what i encourage you to do, then they will know in theirs A/B testing that users actually really prefer old layout. 176.221.123.255 12:10, 26 January 2023 (UTC)
 * I agree that the new design isn't ideal. I am most frustrated by the large borders/sidebars on the sides of desktop monitors. Why squish all content into the middle of the screen and leave these massive blank rectangles on the side? Less information on the screen at a given time = bad, in my opinion. That is my main gripe... I like the idea of a sticky table of contents, but I am too jarred by the sudden change in page size relative to monitor resolution/aspect ratio. Donlad26 (talk) 15:50, 26 January 2023 (UTC)
 * I too can only agree. The MASSIVE amount of whitespace introduced is a complete backwards step that I cannot believe passed to the end. 2A01:4B00:8786:D00:9CCA:920:18FE:893D 19:40, 26 January 2023 (UTC)
 * I was using the "?useskin=vector?useskin=vector" thing to force the old design, but that stopped working it seems. So here I am, a glorious, new registered user.  My username conveys my feelings on the matter. Yournewdesignsuuuucks (talk) 19:41, 26 January 2023 (UTC)
 * 100% agree. At first I thought I'd accidentelly opened the mobile version, but then to my shock realised that someone at Wikipedia apparently thought it was a good idea to make this the design of the main version of Wikipedia. This should be reverted asap and the person who greenlit this should be fired. Luckily there is an option to switch back to the previous design, but the user experience should be good out of the box without having to manually change some settings first. -- Cyberhopser (talk) 18:35, 27 January 2023 (UTC)
 * Oh wow what a worseification.... i hope next time they beg you for donation they receive at most only 1/4 of the usual, clearly they have to much money to waste.
 * - Language selection, much more inefficient
 * - New right side menu distracting from the article
 * - Horrible, completley unusable new TOC
 * - Switching from a design usable at all resolutions (usually i even preferred it on mobile, as i didn't like the castrated mobile version aswell) to a fixed width is a massive step backwards too. (As others noted already: lots of wasted space) BorisSapulu (talk) 18:39, 27 January 2023 (UTC)
 * It is quite awful, and I created an account to revert to the old layout. 198.102.103.103 01:25, 28 January 2023 (UTC)
 * echoing here the new ui is eye bleed inducing i feel as if i will get a headache looking at it for too long. the cramped appearence makes reading anything a chore and makes things ugly with the spacing what is with that planing to add huge banner ads? the only reason i made an account was to revert this change will likely cause some people to leave if its not fixed this should be an optional theme not the defult your going to have infogalactic eatting your lunch. change for the sake of change is never good, if you need your ui design team to earn their keep then have them work on optional skins for the end user to select. the mobilefication of the net needs to stop theres a reason .m exists use it. Bobboter (talk) 05:13, 28 January 2023 (UTC)
 * I made an account specifically to save my preferences regarding the appearance. I'd rather check wikipedia on my phone than go through the 2022 layout. Awful. VangyTuft (talk) 08:24, 28 January 2023 (UTC)
 * I do agree with you - like I agree 100% with everything you said - but you can change back to the original layout, so I'm not too upset. I don't really see them taking away the legacy layout either. 2604:3D09:A977:3600:5DEE:6E28:6C0:7871 11:14, 29 January 2023 (UTC)
 * Yep. I actually registered on Wikipedia just to have the preferences option to switch to the old layout. It's just amazing how bad the new one is. Yegork1978 (talk) 19:29, 29 January 2023 (UTC)
 * About the only 'positive' is a separate TOC, and even that is rather badly implemented. It should be the topmost left table, separated from other menus and options, aligned with the article. Vinner19 (talk) 21:35, 29 January 2023 (UTC)
 * I totally agree!! I can live with if design is not too nice-looking, but I hate when it's unpractical. And this new look is just too horrible to use. I often switch languages, sometime even those I don't talk or read, only now its impossible task to do it quickly with that stupid select box, if there are twenty languages. Moreover, I have to log in in each language to set old layout, that is so very annoying. I could write quite a list what else is useless, but I see others wrote it down already. BeaBeta (talk) 23:38, 29 January 2023 (UTC)
 * Yes. I do not understand the disregard for users screen space. I purchased a large monitor only to find that 'designers' throw away large parts of it's space. An wiki page is not there to look beautiful (not that you could call the new design beautiful! but at the end of the day I suppose that's a matter of taste.) It's form should start with and follow function; it's there first of all to provide information, and options at your fingertips. Both are reduced significantly.
 * I am very glad to be able to switch back! 2A02:A46A:A337:1:14E3:853E:3CB2:6782 09:02, 30 January 2023 (UTC)
 * The new layout is EXTREMELY inaccessible for people with disabilities in my opinion.
 * The text being all smashed together is harder to read, the white space is distracting, and the god awful hamburger menu requires extra movements and clicks to open. Everything is so unintuitive, frustrating, and makes my head hurt. I imagine people who need screen readers are having an even harder time than I am using this site. People shouldn't have to make an entire account just so they can use an educational website without suffering.
 * Wikipedia 1000% did not have people with disabilities in mind when working on this redesign and approving it, as seems the case with most websites who push for the atrocity that is "modern" web design. I wonder if Wikipedia realises they aren't required to follow the the trend of having an ugly website that's terrible to use.  Azethes (talk) 09:11, 30 January 2023 (UTC)
 * I think it depends on the person. I have disabilities and prefer the new layout. The previous desktop version looked to me like an overwhelming wall of text. Each line was so long that I couldn't keep track of what I was reading, and constantly moving my eyes from left to right across that wide field caused fatigue. Screen readers helped me maintain focus, but I would just opt to browse on my phone instead.  The new layout provides short, digestible lines of text, and the white space creates a cleaner, focused appearance. I do agree that modern web design sucks, but I find this revamp to be helpful. Otherwise, I would love to use MonoBook!
 * I'm sorry you're having a difficult time with the new layout. It looks like many people are in the same boat. I'm glad we are able to toggle between different layouts in order to figure out what works best for us. All I can say is that I'm thankful to have the new layout as an option. TheCowboyPirate (talk) 08:39, 1 March 2023 (UTC)
 * The only good thing about the redesign is the TOC sliding down with us on the left as we scroll the article. Everything else is bad. The one thing we could have used is a dark mode and we're being told it *was* technically impossible to do, has recently become possible, but won't be done regardless. I've never heard anything like it. 81.100.55.96 00:26, 31 January 2023 (UTC)
 * THANK YOU. It looks SO bad dude. This needs to be reverted ASAP. Thank god they at least made it easy to change back. Sleampy (talk) 23:30, 31 January 2023 (UTC)
 * Agree. Created a Wikimedia account today to change my theme preference, lol Jessveness (talk) 07:35, 2 February 2023 (UTC)
 * I am so glad I am not the only one that thinks the new layout is god awful! I thought I was going insane when I was google searching "new wikipedia layout" and all the top results were news articles with headlines like "Wikipedia gets its first makeover in over a decade… and it’s fairly subtle" (link). I was so happy when I found out that I could get rid of the layout by logging into my account. Sockbucketfrance (talk) 08:35, 2 February 2023 (UTC)
 * Definitely agree. New look is a piece of shit. Hire some UX designers! and think twice - it looks ugly on the huge PC screens! 213.210.175.85 12:05, 3 February 2023 (UTC)
 * Couldn't agree more. It is absolutely horrible. 213.160.161.52 21:56, 3 February 2023 (UTC)
 * I was trying to save my appearance preferences to one of the older themes, and it straight up will not apply. Every time I re-visit a wikipedia page it is set to vector 2022. Is there a fix for this? I've already cleared my cache/cookies. CapSAR (talk) 03:40, 5 February 2023 (UTC)
 * I agree! this needs to be revised back to the older verson by default. Webpages need to be functional, and not minimal. The new layout is not even optimized to view more text! Haldardhruv95 (talk) 05:57, 5 February 2023 (UTC)
 * i fully agree!
 * been using wikipedia for all my life and this new ui is a major shock, whos fucking idea was it to change it without a poll or something? Zekromisblack (talk) 00:56, 6 February 2023 (UTC)
 * I am more worried if it gets worse, like when they start introducing a fixed sticky nav toolbar in the next design (I thought they listened in 2020) and ram it in yer face constantly as you scroll the page where it is in the way and distraction.
 * I am totally against it. It should be down the user what they want to see constantly on their viewing and not a few people who think they want it stuck constantly against their wishes in the guise that it will help and the users are somewhat stupid and confused.
 * They will loose my donations once they do that on Wikipedia. MrMobodies (talk) 02:45, 14 February 2023 (UTC)
 * Agree, less intuitive, less effective real estate. Suggest making it optional, not default and seeing how many actually opt-in. Saucypuck (talk) 01:23, 8 February 2023 (UTC)
 * Have to agree, unfortunately. While I don't have a flickering issue, the layout is absolutely terrible and seems to combine the worst of a desktop and mobile layout in one. Please go back to the previous default and save us from the weirdness of wasted space combined with restricted element sizes. There's no reason to make such a change here - sometimes something is just good and you should leave well enough alone. P.S.: it's not "subtle". Wolfbeast (talk) 08:19, 9 February 2023 (UTC)
 * I agree! I made this account just to change to Vector legacy... I love you Wikipedia but this new layout has go to go! 178.55.41.49 10:04, 11 February 2023 (UTC)
 * I would also like to express my discontent with the new layout. Like many people here, I've made a wikipedia account just to go back to the old theme. 79.186.222.249 17:26, 11 February 2023 (UTC)
 * I'm a long time donator and small time contributor to wikipedia, and I add my voice to what appears to be hundreds of others concerning the layout change. It is incredibly cramped, counterintuitive and disorienting, and overall much worse than before. "Improvement" for the sake of improvement is a modern plague. Considering the overwhelmingly negative nature of the feedback I see here, why isn't this change reverted at once? Numero4 (talk) 06:49, 12 February 2023 (UTC)
 * I know, why is it under desktop "improvements" Higuys153 (talk) 04:52, 13 February 2023 (UTC)
 * I cannot claim to be an expert in editing Wiki pages, but as a retired academic I have a lifetime of reading journals in science. I'm now not too well and most of my Wikipedia-reading is done on a 15" laptop while sitting in a reciner chair.  I typically spend hours a day reading it.  I also take the trouble to donate for this :-)   I use Firefox and I have a large collection of bookmarks, which I normally keep visible on the LHS of the screen.  For a little  while I have noticed that the longer pages of Wikipedia have lost their valuable pale blue indexes, so useful because as you read parts of a page, the sections you have previously visited change colour.  Very recently I have discovered that if I close down my bookmarks view I see a sort of quasi contents list (with nothing of the precision of the old contents lists).  Also, there is stuff on the RHS that I hardly ever look at (was it ever there before?).
 * Today I have looked around and discovered this "skins" issue, and if the changes I am witnessing are anything to do with this, then I don't like it - AT ALL. The old American saying "If it ain't broke then don't fix it" comes to mind. I pretty much agree with all the above complaints and I think it's time Wikipedia did a "revert".  I note some commentators suggested that the new presentation should have been an option to opt into for a year or so; that would heve been much sounder treatment of us users.
 * At this point I have just gone to my desktop with its 24" screen an run up tabs showing the Vector 2022 and previous skins. To me it's no contest: lots of white space on the new skin, pleasant document-style layout on the old.  Anyway, as I now know how to view pages using the old skin, that's what I'll be doing. Bicyclic (talk) 16:51, 13 February 2023 (UTC)
 * I see a SPAMMY FIXED HEADER here but thanks to this extension (CAN'T BELIEVE I expressed my concerns in 2020 to grant user a choice that I am at the liberties of browser extension like this one:
 * Chrome: Sticky Header Hider aka Fixed Header Fixer
 * Firefox:StickDucky
 * This page looks nicer
 * "Currently, many functionalities on wiki pages are only available to users at the top of the page."
 * NO I DON'T WANT THAT.
 * Main page:
 * "This becomes problematic on longer pages, when scrolling past the first few paragraphs means the user would need to scroll back up to access the tools and other resources again." I'd rather do that than have something slapped in my face constantly. Dont under stand how annoying that is". RUBBISH! Put on the side panel then.
 * If ANYTHING IS problematic it is having fixed nav toolbars and widgets rammed into my faced constantly and follows down the page as I scroll away from them totally unwanted and undneed and they are still there in the way and as a distraction.
 * "Our proposed method of addressing this is to make the site header “sticky” This means it stays fixed to the top of the screen (above the content) as you scroll up or down the page."
 * No I DON'T WANT THAT. That is NOT HELPFUL THAT IS ANNOYING.
 * It wasn't a problem before LEAVE IT ALONE.
 * Absolutely no regard for the preferences from users.
 * The side panels was fine as long as I can hide it. But when you start slapping things that span the top the follow down the page, unable to hide it that maybe unwanted by the user as in in the way, that is what I class SPAMMY BEHAVIOUR. Reminds me of the browser toolbars that came installed with flash player and adbobe web installers and also the so called "free games" last decade.
 * The tools above I see in this form that seems GOOD enough until you take them away and put them on the spammy toolbar that gets hidden by the extension.
 * Developer: "The users are very stupid and confused and don't know what they are doing, they are naturally born with a very low IQ level and low abilities which means they can't navigate websites and can be very challenging for them so a fixed header will help people in that it is always there if they want it or not which means it is quicker and easier to get to... lets plaster it everywhere for their own good."
 * No I don't want it. I want it left alone.
 * So far so good on the exisiting wikipedia. I don't sign inI just read articles. As soon as I see a fixed nav/header/toolbar on Wikipedia you can forgot the donations.
 * I do not have difficulty using it, I do however have great difficult navigating a website with unwanted fixed things that are in the way of the contents and serve as a distraction. instead of flowing with the rest of the page. MrMobodies (talk) 02:20, 14 February 2023 (UTC)
 * The new look is awful, with far too much white space. Perhaps Wikipedia should provide users some simple control over the appearance. And perhaps browser makers could get together and incorporate some sort of "style" preference (eg. navigator.style="[compact|mobile|desktop|...]" then every web site could automatically provide multiple css choices accordingly. Unfortunately CSS has become grossly convoluted and overly complicated, as have the javascript intrusions. Really this whole UI mess needs a lot of cleaning up. 208.71.172.42 03:05, 14 February 2023 (UTC)
 * It looks like it was designed for mobile not desktop, absolutely terrible and unneeded change. I hope they're listening instead of burying their head in the sand until the criticism dies down then declaring it a success based on people giving up. Thenewdesignisterrible (talk) 07:15, 14 February 2023 (UTC)
 * Replying to concur, the new layout is terrible and highly inaccessible. The design is completely inappropriate for Wikipedia. Freedom4U (talk) 03:33, 16 February 2023 (UTC)
 * the new layout is terrible on desktop, *especially* for a multilingual user like me 2601:600:C980:2DA0:80BF:252A:BF4:8EBC 12:08, 18 February 2023 (UTC)
 * I agree, I hate everything about this new layout Muddiebuddie (talk) 04:09, 19 February 2023 (UTC)
 * Agreed. Had to switch back to Vector Legacy 2010 in Preference here:
 * https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering Intrepid-NY (talk) 16:11, 21 February 2023 (UTC)
 * agreed. looks worse and harder to read 128.6.36.140 20:16, 27 February 2023 (UTC)
 * Agreed, Vector and in particular the left hand 'bookmark' or whatever it's called removes too much content. The previous version (2010) was much easier to read in my opinion. Can we improve without taking away too much of the content which the reader wants to read? Textualism (talk) 11:11, 28 February 2023 (UTC)
 * Agreed, I had to make an account just to get the old layout back.
 * For me the most annoying thing is that the language selector is hidden in the new version. As a multilingual user I usually read articles in all languages I can read to get the most of it. 88.115.148.22 07:18, 3 March 2023 (UTC)
 * The only reason I made an account was to revert it to previous layout and provide feedback on how much I HATE this new layout.
 * It reminds me of when someone sends you a mobile link on desktop and the .m.wikipedia in the URL causes it to look poorly formatted with a bunch of useless white space. RevertToLegacyLayout (talk) 08:21, 3 March 2023 (UTC)
 * Agree 2A00:23C5:DC80:6301:0:0:0:1083 16:00, 19 March 2023 (UTC)
 * As a 17-year-old Wikipedian, I completely agree. The new look (2022) is terrible. It is not acceptable to me. I went back to the "2010" look. Radek68  (dyskusja)  06:59, 27 April 2023 (UTC)  Radek68  (dyskusja)  06:59, 27 April 2023 (UTC)

Came here to say the new layout looks horrible. Whose idea was this? 69.245.61.93 17:32, 23 January 2023 (UTC)

Signed up just to agree how horrible the new layout is. I have a 2560x1440 display and the new design uses 1/3 of it. Why are we treating desktop sites like mobile sites. You HAVE a mobile site, mobile.wikipedia.org, use that for you vertical/skinny text display. Stop taking away my screen real estate, you are NOT fandom. Stop ruining your website experience. --Kinomora (talk) 21:30, 31 January 2023 (UTC)

It's growing on me. But there's always the option to stick with the old layout. I just got here by clicking through the "preferences" menu. PaulHammond (talk) 19:32, 23 January 2023 (UTC)

Vector 2022 must die.

Agreed, I made an account just because i read you can change the layout back to the original and when the survey asked what reason i had for creating my account today and since it didn't allow me the option of telling them to delete this new layout i'm posting it here

I agree, the new design sucks. The one function I use as a multilingual person - changing language - has for some reason been hidden behind a drop down gadget. "More prominent" my ass, it's much less usable now than simply clicking on the language on the left side. --2A00:5500:80E8:AB00:0:0:0:100 18:01, 24 January 2023 (UTC)


 * This was the key problem that drove me to log in and setup preferences. Frequently change languages. Used to be a consistent annual donor, but clearly they don't need the money if there's budget to waste on removing all the functionality out of a UI that wasn't broken. Everyone who signed off on this, the whole way up the management chain should tender their resignation immediately. Dvulrich (talk) 20:30, 25 January 2023 (UTC)
 * Fully agree with you! I don't get why websites that are LONG established and work perfectly fine feel the need to be..... *sigh* [record scratch, turns baseball around] HIP! With it! In with the crowd! Not like your parents! So don't frown! [end lame 90's nonsense that ad companies though was cool] They need to stop. They all need to stop. Pinkfluffyunicorns88 (talk) 03:29, 4 February 2023 (UTC)
 * It is more prominent. English is not my native language, but the majority of articles I read, are in English. Every now and then, I change between English, Norwegian, Danish, Swedish, and a few times in the past, even French. Heck, I've even looked at articles in German. I prefer the new drop-down in favour to the old list of languages. Now the languages are always in the same spot, there's no long list of text claiming attention when I don't need it, and most importantly: no more need for scrolling to change language. That was so annoying about the old design; having to scroll down.
 * And now that I'm here, I'd like to inform you that the old design was not perfectly functional. I've tried creating a dark mode skin on top of Vector, and that's a truly horrible experience. Technologically, the old Vector skin was terrible. And it was not built for the screens of today either.
 * I hope the redesign of Wikipedia can bring us a much easier experience for building custom skins. Imagine, a future with lots of skinning abilities. Where those that want thick borders get that, those that want no borders get that, you can freely change between light and dark modes without issues, etc. Andcraft (talk) 04:03, 26 February 2023 (UTC)
 * ad "That was so annoying about the old design; having to scroll down." - the hell... instead of short scroll down I have to scroll all the way up now and then click and scroll again...
 * what a symptomatic for all the "new, thin, clean, lightweight" hipsterish design... in the end, less information, worse navigation and more scrolling and clicking 213.220.196.10 14:01, 11 April 2023 (UTC)

Totally agree. Vector 2022 is horrible. Full stop. Please at least do not make it default. I know how to revert it with or without an account (just use a browser add-on named ‘Redirector’ and write some rules), but the ugliness and the user hostility shown in this design are beyond understandable. Chu Tse-tien (talk) 22:22, 9 April 2023 (UTC)

I concur: this 2022 as a default is a horrible waste of page space. 99.73.36.110 01:43, 25 January 2023 (UTC)


 * Same here. Not only doesn't it look like anything educational, it wastes space on any screen bigger than 8", and the stark whiteness leaves you lost in space. I switched back to the one with the book, that at least looks pretty. 92.200.175.206 20:36, 29 January 2023 (UTC)
 * The new layout of Wikipedia is horrible, we all know that at this point. But I noticed something entirely else. The English version of Wikipedia is downgraded with this Vector 2022 nonsense but the German and Russian Wikipedias use the superior old Vector 2010 layout. Yes this is true-you can check this right now if you don't believe me. I do not know Russian or German language, I was just clicking around to see what is going on with their layouts. So good for them and for English readers we get the bad user experience.
 * Why the team that works on this decided that the English readers and editors should be tortured with this new layout?! How and when the other non-english communities have negotiated to be spared and not suffer the Vector 2022 disaster??? They have their voice heard and opted out but we the English using community are second class citizens now? How the other communities managed to convince you and we fail when we say we do not like Vector 2022? 94.26.15.134 16:29, 30 January 2023 (UTC)
 * Agreed. This is a massive downgrade on anything but a small phone. Varixai (talk) 16:19, 13 February 2023 (UTC)
 * Created an account just in order to keep reading in the legacy layout... The UX for a multilingual user is terrible, you need to click your way through some pointless language menu rather than just select the language from the box to the left (where you also instantly see in which languages the article is available). And besides, on a UHD screen 70% of the screen surface is displaying nothing... Why would you do that? That's what the mobile layout is for, isn't it? It can be safely assumed that desktop users are using horizontal displays, so why optimize for vertical displays?
 * I really hope that this way of design does not become the new standard. Wwlaa (talk) 22:48, 5 March 2023 (UTC)

I'm making a wikipedia account just to get away from the waste of space.

Make an account? - Thank you, I didn't know about that. Vector legacy is really a more enjoyable experience. It's why people go to cinemas even though they can watch at home. What a difference. Changing the format for mobile is understandable but doesn't make sense for desktops.Preroll (talk) 16:21, 5 February 2023 (UTC)


 * Just another who thinks this 'new look' is nasty, harder to use, harder on the eyes, just plain annoying, effed up bs.  😨😡 Wikiwavy (talk) 17:24, 10 February 2023 (UTC)


 * This mess seriously undermines the credibility of Wikipedia -- as if Wikipedia didn't already have ENOUGH credibility problems.


 * The previous "skin" was clean, clear, matter-of-fact -- giving Wikipedia at least the appearance of being a no-nonsense reference -- and was far easier to use.


 * Where did the article's Table of Contents (ToC) go? It's no longer visible (unless you poke around and find the pop-up, which -- if it's a moderately long ToC -- scrolls off the screen, and is horribly awkward and frustrating to use.


 * I finally figured out I could undo the damage, at least when "I" view it, by making changes to the "Preferences" setting (I'm a Wikipedia "Veteran Editor," extensively certified computer professional, state-licensed educator in computers, and former award-winning web developer, so I should have been able to figure out a personal solution, but it was not obvious) -- and MOST ordinary (non-editor)  Wikipedia  visitors will have NO idea the option exists.


 * This screw-up is what happens when you let some amateur idiots make changes for the sake of change -- they'll "fix" what isn't broke, break it as a result, and then shout "Progress!"


 * Raises extremely serious questions about the leadership, governance and future of Wikipedia. Penlite (talk) 13:05, 12 February 2023 (UTC)
 * What do we have to do to get this eyesore reverted? It's honestly the worst change I've ever seen. Dyaluk08 (talk) 10:24, 26 February 2023 (UTC)


 * '''I finally figured out how to go back to the old look, or so I thought. Only works for the one page you are on. Surf to another page, ugly look is back. StyxinConn47 (talk) 18:05, 2 March 2023 (UTC)
 * Wanted to add that taking the advise of someone at Wikipedia, I logged in and was able to set a preference to revert page format back to the old look, which I did immediately. I cannot stand the way they shoved all this empty space on the pages over to the left side, while the meat of the site takes up the right two thirds of the screen. But now when not logged in, the "[Hide]" switch above the wasted space won't even work. This is with Firefox V. 80 something. This is so crazy. StyxinConn47 (talk) 18:52, 17 March 2023 (UTC)


 * On the assumption that sheer numbers of comments do actually count for anything: The new style is indeed (I'm afraid) really horrible. Depressing to see Wikipedia get sucked in to the current fugly flatso-design fad (that I fervently hope will quickly go out of 'fashion' soon once everyone sees it for the emperor's new clothes that it is). Painfully searing white everywhere (the previous theme wisely used gentle off-whites and grey shades to elegantly put secondary UI areas into the background and make for a more relaxing reading experience). From an accessibility perspective the biggest loss for me is the lack of that good contrast and vertical line separator between the left hand menu and the main content area: now all just an endless sea of indistinguishable searing white, and, when I am reading, without those subtle but essential separation cues (and with an excess of horizontal whitespace that doesn't have the needed tight margins to even remotely work as a "newspaper column" substitute), my eye is irreversibly drawn to the left hand edge of the window at the end of Every Single Line, causing a real 'low level' brain 'glitch' in trying to read. Ugh! --Davecykl (talk) 21:42, 14 March 2023 (UTC)
 * I agree, new design is horrible. I think the new design is very wrong way. We are in 2023, full HD, 4K, 8K, big screens, etc... why should we make narrower pages, websites??? Wiki has already responsible mobile version. For example many people are using 1920x1080 screens, in this case many pages with lists, columns with lot of information, images are broken now (I edit many of this). The left area is total empty and unused in most of the Wiki pages. And there is a big white gap on the right side of the Wiki pages also. What is the reason to make the content, the information so narrow??? Check out these pages with new and old design: I support to revert the narrow layout of the new design. OrionNimrod (talk) 10:30, 15 March 2023 (UTC)
 * As desktop computer user on Firefox, I agree with posters here about the new Vector 2022 design more difficult to navigate, less intuitive. For example, the index of sections in an article has disappeared in Vector 2022, and when I re-size browser, the index of section re-appears. Which (sub-genius) designer dreamt up this useless feature to inflict upon us?! Previously this index was static right below general summary. And so many other intuitive features/layout in Vector 2010 have now disappeared to make life so much harder for Wikipedia users. If Wikipedia is trying to lower readership with Vector 2022? Congratulations the Vector 2022 layout has soured my Wikipedia user experience that I think 3 times before clicking on any Wikipedia link now. Thank you Wikipedia for breaking was was NOT broken. Puffin10 (talk) 16:47, 15 March 2023 (UTC)
 * It's narrower precisely because we have larger screens. If there were content on every part of the screen, without any margins, then people would have to constantly swivel their heads side-to-side. I have a 32-inch-monitor and I don't want to have to adjust the size of my entire web browser just to be able to read one website without straining my neck. Galactipod (talk) 13:35, 30 March 2023 (UTC)
 * Just to add to the chorus of voices here - it's a bad new design, the last couple of defaults were both good. The new one's not without some silver linings, floating TOC is nice, but it's a very big downgrade overall. In particular the whitespace is an assault on the eyes and it's sad to see yet another website make this same mistake - an absolute cardinal sin of UI design in my book. I really hope it gets reverted back to Vector 2010 as default - I'm yet another IP user who now uses an account solely to avoid the redesign but as I use a VPN this is not exactly convenient. --AcumenDonor (talk) 10:59, 21 March 2023 (UTC)
 * Everybody expressing oneself here (in a very respectful way...) is just having a basic reaction to a change.
 * Name ONE quality website that hasn't been shrinked in width?
 * You are talking about user experience, but you are talking about your own habit only: how can reading a sentence on a 50cm width is a good user experience?
 * It also solves one of the main layout issues by being accessible by any kind of screen shapes: before, every contributor was changing the image organisation according to his own device, never caring about what screen others could have. Now everybody has the same layout: how can this be a problem?... Daehan (talk) 12:59, 21 March 2023 (UTC)
 * It's been two months. Maybe you could write it off as a reaction to change if it was two days in but the dust has settled and it's still not going down well. Personally I delayed posting (and missed the votes) precisely to not have a knee-jerk reaction, but my negative reaction is actually quite a bit stronger now than initially. I've definitely seen worse redesigns but decent ones, and even many bad ones, don't usually still rankle months later.
 * I'm not going to spend too long on the irony of saying "you are talking about your own habit only" and then immediately talking about your own preferences, but I will point it out.
 * While we're talking subjectivity - my display is 50cm across, I have my web browser at full screen and, yes, I prefer reading like that and yes, subjectively, that's a good user experience. In contrast the ~60 characters per line that's often posited as the optimum line length is nigh-on unreadable for me on a monitor, though fine in print. I don't know how solid the evidence is that this is any kind of optimum (I'm very sceptical given how vague the usual source given is) but it certainly isn't a universal optimum!
 * Fortunately the new layout isn't quite as bad as that but I personally never experienced the issues you had with the old layout (not to say they don't exist, but they're clearly not that major) and think the old layout was better at accommodating different tastes and was therefore a better default. Especially given logged-out users can't set layout preferences with cookies. --AcumenDonor (talk) 15:28, 21 March 2023 (UTC)
 * As a person with a 32-inch-monitor, the whitespace is lovely. The content is exactly where it's comfortable for me to look: in the middle of the screen. The alternative is constantly swiveling my head side-to-side and straining my neck. Galactipod (talk) 13:42, 30 March 2023 (UTC)

Dark Mode
Make any theme with native Dark Mode. Time for filling everything around with any color, on condition that it is "white", has passed.

Seregadushka (talk) 21:45, 7 November 2022 (UTC)


 * someone had a decree of the Ministry of Health of the United Kingdom on reducing the brightness of monitors. I can't find the link. The savings were measured in hundreds of millions of F (reduction of electricity consumption, equipment resource, treatment of eye diseases, payment of sick leave, ...). It's time for Wiki to listen to this. Seregadushka (talk) 00:26, 8 November 2022 (UTC)
 * Native dark mode is necessary for global environmental friendliness and for a better experience.
 * It reduces power consumption when using OLED displays.
 * Also, white screens are very glaring when transitioning from other dark-mode enabled websites. (And the new theme is more "white"!) Futchitwo (talk) 17:29, 9 November 2022 (UTC)
 * @Seregadushka, @Futchitwo, thank you for your comments. I've just updated our answer about dark mode in the FAQ.
 * In short, we are not going to do that as part of this project. At the beginning of the project, we would even say that it's not possible. It has become technically possible recently, though, and someone at the Foundation could work on that.
 * Perhaps you would consider taking part in the Community Wishlist Survey and voting for dark mode? This is an easy way for editors to ask for a specific technical change. The period for making proposals will be in January, and voting would be around late January - early February. (See the Wishlist's FAQ to learn how to take part.) Thank you! SGrabarczuk (WMF) (talk) 22:55, 9 November 2022 (UTC)
 * I can't figure out how to participate in the survey. Where is the choice of questions ? 4 periods are specified, but there are no actual tasks of this survey. Prudently. On the topic -- now absolutely all operating systems of mobile phones and computers have "Dark Mode". Stop hanging around in the past, when there was nothing but a white Apple. If the design is only white? My eyes hurt from the work of your designers ! Seregadushka (talk) 03:27, 16 December 2022 (UTC)
 * Hey @Seregadushka. We also believe having the dark mode would help. As I wrote, this mode has only been made possible recently, as a consequence of this project. (The Survey hasn't started yet - the first phase will start in January.) SGrabarczuk (WMF) (talk) 16:11, 16 December 2022 (UTC)
 * And my eyes hurt when I try to read bright text on dark background. Also you seem to be (deliberately?) forgetting that even Apple I had white text against black background (as did Apple II and MS-DOS) - I'd say there's a reason we moved away from that. 2A02:A312:C539:8D80:78DE:760D:452F:23E2 19:58, 19 January 2023 (UTC)
 * Talk:Reading/Web/Desktop Improvements|I see you don't even mention these reasons, because there is no reasonable explanation for this. What you don't know how to do working with CSS styles is not the reason. The whole world is striving for green technologies. But you don't understand (intentionally?) that millions of monitors operating in the mode of maximum energy consumption disrupt the general movement of humanity to reduce the impact on the environment. Hire other programmers who understand CSS. Seregadushka (talk) 23:26, 19 January 2023 (UTC)
 * "At the beginning of the project, we would even say that it's not possible."
 * This is a completely false statement. From a programmer's point of view I can guarantee everything that such a change is extremely easy.  But on a LARGER NOTE -- the Wikipedia Android Mobile App has had dark mode for quite some time.  And the time is far overdue for the web interface to catch up and stop being both a drain on electricity and a strain on eyes. ClimbAll (talk) 09:34, 21 January 2023 (UTC)
 * I wouldn't call dark mode easy, or impossible. Somewhere in the middle. There are dozens of CSS elements you never think about or notice until dark mode messes them up.
 * I have been using Skin:Citizen for quite some time on my wiki with very few problems. It has an excellent dark mode that automatically engages when user browser preference is set.  I think WMF should make it available for logged in users. Flounder ceo (talk) 16:18, 31 January 2023 (UTC)
 * Hello from a fellow programmer. I have tried making a dark mode of the legacy Vector skin. It's horrible. You are very much wrong when you say that it is extremely easy. It seems like you have very little experience in this field. Building a system with both light and dark modes from scratch, isn't so bad. Wikipedia wasn't built for that, and the articles written since were styled for a bright interface.
 * I also use the mobile app, and in a dark style. I like it. But you can't escape from the fact that the mobile app was built almost from scratch, and that there's several visual problems with it.
 * The Wikipedia system wasn't constructed for this. It seems like the new one is enabling that. That's great. Andcraft (talk) 04:13, 26 February 2023 (UTC)
 * > At the beginning of the project, we would even say that it's not possible. It has become technically possible recently, though
 * This is an insane thing for you to have to say. If the redesign made darkmode impossible and it has only recently allowed for it for be done very difficultly, you should consider whether the redesign is any good at all. 81.100.55.96 00:15, 31 January 2023 (UTC)
 * Hello! Let me clarify, I meant this project has just recently made it possible to build the dark mode. Before that, with the previous skins and in the early stages of the project, it wasn't possible. SGrabarczuk (WMF) (talk) 02:01, 28 February 2023 (UTC)
 * I am astounded that after such a large update to the UI, native dark mode for desktop is still not a feature. Frosck (talk) 23:31, 21 January 2023 (UTC)
 * In fact, I made a naïve assumption that a native dark mode would be a part and parcel of the new UI— calling it "not possible" is laughable at best TheLucifer0509 (talk) 04:20, 22 January 2023 (UTC)
 * I absolutely agree with this. I can't add much to the discussion, but I feel this NEEDS to get to Wikipedia. Vicente Valle (talk) 06:54, 10 April 2023 (UTC)

There are several dozen applications for Windows browsers, that have the conditional name "Dark Mode". One change the display for ANY site. And they are practically not mistaken. I.e. they have a universal mechanism of operation for all Internet sites. And you can't make a "Dark Mode" specifically for Wikipedia, when you don't have to guess, all the properties are known. Almost always people make decisions (and answer questions and suggestions) who understand little in questions asked. I'm not a programmer, I haven't sold a single website, I'm not paid to know CSS, it's a hobby for me. As the programmer ClimbAll (talk) has already said, this is extremely easy to do:

And that 's all ! Currently, the whole Wikipedia works on the same CSS style, only the properties are swapped (even if you use PHP, it won't be much more difficult). You only need to provide switching  and Of course, you can choose different colors for texts of different purposes, different degrees of "grayness" of the background of the pages. But these are conventions. I assure you, the entire amount of work will not go beyond 10 KB :) Seregadushka (talk) 17:36, 24 January 2023 (UTC)


 * For users interested in Dark mode who have not yet participated in the related discussion of the Community Wishlist Survey 2023, you can do so here meta:Community_Wishlist_Survey_2023/Reading/Dark_mode. Patafisik (WMF) (talk) 11:07, 31 January 2023 (UTC)
 * Last year WMF removed dark mode from the wishlist. Flounder ceo (talk) 16:07, 31 January 2023 (UTC)


 * The Wikipedia App has already two different dark modes and a sepia one. On the desktop I always use the firefox add-on Dark Background and Light Text by Mikhail Khvoinitsky with the option "Stylesheet processor", but sadly not everything is displayed correct at Wikimedia-Projects. Links are all blue for example. Also it takes more cpu usage instead of loading a native darkmode site. --KleinerKorrektor (talk) 19:34, 18 February 2023 (UTC)


 * As an aside/work-around, the Dark Reader browser add-on, available for most common web browsers, is a very useful add-on which generates a dark mode for any website as the page loads. --Davecykl (talk) 22:11, 14 March 2023 (UTC)

Some opposes and supports with same argument

 * Moved at https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Rollback_of_Vector_2022#Some_opposes_and_supports_with_same_argument

Links on whitespace (table of contents, etc.)
I'm using the new layout for quite some time now and I like it. Great work, thanks!

One thing I absolutely hate, though: In the left-side nav bar, all the links seem to cover the full width of the bar, even if the link text is much smaller. So e.g. if there is a table of contents with the two chapters "Some very long text" and "Short", the white space right of "Short" will link to the "Short" chapter as well. It's effectively a link like "Short _____________", where the underscore line is invisible, but anyway linked. While I personally don't see any usecase for this (if I want to open the link, I would click on the link text and not just somewhere around it, would I?), I see a disadavantage of this multiple times every day: When I want to scroll through a long page, I habitually middle-mouse click some white space on the page to enter the browser's fast scroll mode. Works in any browser and almost all websites (the only common exception: ads), just on Wikipedia I now have to be very careful where to do this, and frequently end up in opening a new background tab instead of scrolling. Karotte Zwo (talk) 09:13, 22 February 2023 (UTC)


 * Hello @Karotte Zwo. Thanks for reporting this. What OS and browser are you using? I presume you have seen this on German Wikipedia, am I correct? SGrabarczuk (WMF) (talk) 15:52, 10 March 2023 (UTC)
 * Vector2022 table of contents whitespace links.png
 * Yes, German Wikipedia is right, but I also see the same on e.g. English Wikipedia, on Commons or here. Not OS or browser dependant, seeing it on both Chrome and Firefox, and also both on Windows and Android (though on Android I don't scroll by clicking white space, so not an issue for me there).
 * It mostly affects pages with a table of contents that is long but not exceeding the screen, and where most topics have short names. A good example is de:WP:Auskunft, a village pump where topics are sorted by day. See the screenshot: A good part of the whitespace visible in it is linked with the table of contents. If I middle-click where my cursor is in this, I don't enter free scrolling mode as expected, but open a new tab with the same page again. Karotte Zwo (talk) 15:48, 21 March 2023 (UTC)
 * Actually, I find that this design with a large "overshoot" area makes navigation easier and more comfortable. The TOC behaves like a menu with invisible buttons of consistent width. When the user moves the pointer into the TOC area, they can navigate to different sections by simply moving the pointer up and down (or scrolling the TOC vertically) without worrying to hit the text.
 * For this reason, I wouldn't consider the TOC area (and other menus) as "white space".
 * I saw that an interface with "boxed" TOC and menus (bounded with a border or with a different background) is being tested. I think this is a good idea, as this would more clearly delimit them as part of the interface (rather than empty space). --Lion-hearted85 (talk) 12:24, 8 April 2023 (UTC)

New prototype. Visual separation between regions
Hi everyone,

We have been analyzing your feedback on the page layout. We have read the comments you have shared here as well as on the RfC on English Wikipedia, Village Pumps, other wiki pages, Phabricator, as well as at meetings. Here are our updates on this work. We wanted to begin a conversation around next steps on further improving the layout.

Feedback about the white space

Currently Vector 2022 uses whitespace to separate the various regions of the interface. It also has a white page background (outside of the content area). There are two areas of concern about this:


 * 1) Comments about adding more visual separation between regions of the interface. You have been wondering if this would improve the reading experience. Mainly by:
 * 2) * Drawing more focus/attention to the content when landing on the page (rather than taking in the interface as a whole first, then focusing on the content)
 * 3) * Making it easier to stay focused on the content while reading, because the content area would be more well defined (some of you have reported getting distracted by the table of contents while reading)
 * 4) Comments about adding a gray background outside of the content area. You have been wondering if this would reduce eye strain some people are experiencing from the large white area (i.e. “glare”) on larger screens.
 * 5) * Many of you have reported that the white space is too high in contrast and that adding a darker hue such as a gray decreases this strain.

Prototype – proposed changes and tradeoffs Based on this as well as feedback on further iterations, we have prepared this prototype. (T259240) This is a proposal for potential changes. The prototype focuses on:


 * 1) Adding a boundary around both the content area and the table of contents (as well as other menus). Our hypothesis is that this boundary can help to further structure and clarify the interface. It would also make it easier to focus on the content (both when the page first loads, and while you are reading). Note that you can pin the Tools menu using the dropdown on the right.
 * 2) Making the page background gray. Our hypothesis is that this should help reduce the eye strain some people are experiencing. It would also add further focus to the content area and the table of contents.

We are leaning towards the configuration which includes the white header background, borders, as well as framed menus.

But this comes with some tradeoffs. This configuration affects the width of the content. Specifically:


 * It reduces the width of the content when compared to the current version in the case where the page tools menu (the right one on the screenshot) is open.
 * It increases the width of the content when the page tools menu is closed, when compared to the current width.

Our designers are working on limiting the effects of this. They are adjusting some of the padding and margins, which will be reflected on the prototype in the coming days.

Testing

As a next step, we would like to propose an experiment or series of experiments which can validate the hypotheses above. We aim at identifying whether updating the layout in this way would improve reader and editor experiences. We have a couple of different options for this. For right now, we are considering the following:


 * 1) Qualitative testing - run user testing through interviews with readers and editors. These would aim at approximating whether the content is easier to focus on, and whether the new background reduces eye strain
 * 2) A/B testing - run an A/B test on logged-in users, which looks at the key metrics of the project, comparing the current layout to the previous layout. Specifically: opt-out rates, pageviews, edits, session length, usage of the table of contents, and scrolling. Due to our technical restrictions and privacy concerns, we are unable to perform A/B tests on logged-out users. This means that we will use the behavior for logged-in users as a proxy for all users. If the new layout is selected, we will compare key metrics (before and after the change) across all users.

Some of you have mentioned building out a survey that asks users about which layout they prefer. Sentiment surveys can be useful, but we don’t think they are the best tool for evaluations of usability. The reason for this is that we don’t think this type of survey will give us the information we need to confirm or reject the two main hypotheses above.

Our questions to you

We’re curious if the list above sounds good for the feature evaluation. If not - do you have any other ideas on evaluation? We are looking for ideas on measuring whether the new layout helps in content separation or eye strain.

Beyond the evaluation mentioned above, the opinions of our communities also play a big part in figuring out what changes are best. What do you all think of the prototype?

We will invite more volunteers and communities to this discussion. We wanted to ping some of you coming from different communities as the first group of interested editors:

Thank you! OVasileva (WMF), SGrabarczuk (WMF) (talk) 01:15, 9 March 2023 (UTC)
 * Hi. I just got the ping. I don't think I'm the right person to answer on this particular question, because I think that the unpinning to two opening lists is a very good decision, and so I do not use at all the pinned sidebars. Especially after yesterday's deployment of my phab task, which unpins the TOC. So sorry, it isn't a question to me. IKhitron (talk) 01:27, 9 March 2023 (UTC)
 * I think my involvement in the Discord meetings and phab makes my position fairly clear :) I'm a big fan of the current "Zebra #9" prototype, with borders and framed menus. It looks like since my last phab comment, the prototype has been updated to remove the border option (Now always on) and the header background option (Off without framed menus, on with.). While not absolutely required, I still prefer the framed menus myself, but with the central page content framed, that's more preference than need. If framed menus were a preference the user could select, that's probably be nice. Ferret (talk) 01:27, 9 March 2023 (UTC)
 * Hi and thanks for this write up. In A/B tests I would definitely want to see how many clicks are there in left an right sidebar in various variants. Some questions come to mind though (don't know the answers):
 * What does it mean to use the table of contents during reading?
 * What does it mean to use the main menu (left sidebar)?
 * What does it mean to use the tools menu (right sidebar)?
 * Are users distracted or do they want to do some task (do they want to read or do they want to e.g. explore linked articles)... I don't think that this can be deduced from A/B tests alone, but if you have measured clicks on various actions in A/B tests, it could be a good material for preparing tests in the form of interviews. And as a helpful side effect - statistics on the use of various actions in the tool and main menu could also help communities decide to maybe remove or move some links/actions. Nux (talk) 02:06, 9 March 2023 (UTC)
 * Hi @Nux - thanks for your feedback! I've added clicks to the tools menus to the measurement plan (will post the updated plan in the next few days). In terms of your wider questions, I agree that it would be difficult to establish what the ToC and menus are used for only from A/B testing.  We're hoping to cover this part through the user testing.  Right now, the plan is to recreate a session by the testers - for example, asking them to read a paragraph, navigate to a different section, and then read another paragraph.  This should hopefully give them enough exposure to both designs to be able to measure the hypotheses of reading focus and reading comfort/eye strain.   OVasileva (WMF) (talk) 15:13, 17 March 2023 (UTC)
 * The new prototype looks great and really easy on the eye, especially the framed menus. However:
 * The TOC makes an impression that it is too tightly packed: its padding is relatively small ( /  ) comparing to  's.
 * This is how the three boxes interact, as I see them:
 * TOC collapsed, toolbox collapsed: Content box center-aligned.
 * If I pin the toolbox when the TOC is collapsed, content box's left border moves to the right while its right border remains unchanged.
 * If I pin the TOC when the toolbox is collapsed, content box's jumps a short distance to the left.
 * TOC pinned, toolbox collapsed: Content box and TOC left -aligned.
 * If I pin the toolbox when the TOC is pinned, content box remains unchanged.
 * TOC collapsed, toolbox pinned: Content box and toolbox center -aligned.
 * If I pin the TOC when the toolbox is pinned, content box jumps a short distance to the right.
 * TOC pinned, toolbox pinned: Justified.
 * That the interface is asymmetric seems weird. Is this expected?
 * NguoiDungKhongDinhDanh (talk) 04:25, 9 March 2023 (UTC)
 * Thank you for this!
 * Is it possible for logged-in users to set their preferred width on a computer-specific basis? Cookies, maybe?
 * Is it possible to do what you did with V2022 and include different screen sizes? The image you have is good but it's what it would look like on a wide
 * What has actually changed? Like, functionally? Is it just the border color?
 * What about the width that was mentioned so much in the RfC?
 * I also have a few suggestions.
 * Test using enwiki-wide banners, fully randomly. To avoid canvassing, and to limit bias. I don't know how technically possible it is to do it for all (most) wikis, but as many as possible.
 * Opt-in A/B testing, again fully random.
 * Define right now a threshold of success for the qualitative testing/AB testing, and make sure users know about it.
 * Define right now what you mean when you say we would like to propose an experiment or series of experiments which can validate the hypotheses above.
 * Thanks for this addition! Cessaune (talk) 04:46, 9 March 2023 (UTC)
 * A couple of remarks:
 * No idea how to check this with the community.
 * The prototype does not have a sticky header anymore. Is this intentional? I would really miss it.
 * As a rather early (mid-2021) adopter of vector-2022, it appears to me that the skin has become much more cluttered and complicated after the enwiki RfC due to all the requests that have been made there. While some requests are clearly legit and some new functionality is indeed great, I find this concerning.
 * I personally prefer the prototype without backgound color—it simply looks dated with background. Particularly the thin 1px border contributes to this impression.
 * What is okay, though, is the current setup here at Mediawiki.org with a gray background left and right to the viewport, but with no gray background visible between ToC/main menu/tools menu/article boxes.
 * —MisterSynergy (talk) 10:46, 9 March 2023 (UTC)
 * Hi @MisterSynergy - sorry for the late reply and thank you for your feedback! Introducing additional clutter is something we're looking out for as well. Just wanted to confirm that the sticky header is only unavailable in the prototype - we don't have any plans on removing it.  OVasileva (WMF) (talk) 20:09, 27 March 2023 (UTC)
 * Looks great! But a small question the prototype doesn't seem to work without JScript(which is sad) or maybe it's me. Also the prototype seems to not find out about my browser language choice and doesn't suggest it at top of language choice list. Greatder (talk) 11:24, 9 March 2023 (UTC)
 * I am sorry but I don't like it. It is only slightly better than the deployed version. The ToC and user's menus should go back to the way they were in V2010, according to the views expressed by many English Wikipedia editors here and here, and by many others in the discussions above: the ToC inside the article under the lede; the user's menus in the left side column. Æo (talk) 12:09, 9 March 2023 (UTC)
 * Thanks for the invitation.
 * For testing, I would suggest to look at experienced editors, new editors and readers that do not (yet) edit as separate groups and try to use samples that represent all internet users and avoid over-representation of US and EU.
 * It would be interesting to see after say 1 or 2 months what have become the options they actually prefer to use. It took me some time to get used to the new layout, but after that it became my preferred skin.
 * The way the sidebars are used, shown and hidden, feels more natural in this new version. To me, this is a substantial improvement. In the present version I often confuse the vertical slidebar of the Tools with the window slidebar.
 * I personally like the gray background, probably because it is more reminiscent of the traditional Wikipedia look. But if readers and new editors clearly don't share my preference, I could easily do without it. Especially as there seems to be a dark mode in the works too.
 * I share the impression and concerns of @MisterSynergy about clutter.
 * Keep up the good work! MarcoSwart (talk) 15:15, 9 March 2023 (UTC)
 * Thanks for the ping and the work. I'm sorry, I think I don't want to be involved in the process anymore. I personally arrived at a stage where I'm waiting for the process to be finally finished, so that we can finally judge what work will follow for the communities. Imho the current state with the contradictions in user interface is a bad idea and no viable starting point for further work. Also I don't like if functionality is lost (like with the new toc). Best of luck with your work. I'm sorry, regards HirnSpuk (talk) 19:37, 9 March 2023 (UTC)
 * I very much support this demo. I think it looks much better than the current skin.
 * The improvements make it useful for me. MathAfrique (talk) 21:37, 9 March 2023 (UTC)
 * For me, gray background outside of the content area allows to focus on the content, provided that frameless menus are used (the "Framed menus" option is disabled):
 * Vector 2022 Zebra9 prototype with frameless menus logged-in.png
 * The frames and white background of the menu cause the eye to run over the resulting gray sections around several windows, which distracts me.
 * In addition, I would like to refer to many voices in the discussion of the new vector and the argument that the old vector works better on wide and high-resolution monitors, because... it spilled text all over the window. On the contrary, the old vector was ok for narrow monitors and small resolutions. With increasing resolutions (for the old vector), the lines of text became longer and longer, which made it extremely difficult to read and made using Wikipedia (as a reader) less and less comfortable. I do not agree with the voices to remove the white areas to gain more width for the content - that would be a return to long lines that make it difficult to read comfortably. Zdzislaw (talk) 10:53, 11 March 2023 (UTC)
 * @SGrabarczuk (WMF) That actually looks quite nice! I look forward to what gets built next :D Aasim 19:28, 12 March 2023 (UTC)
 * Cool! Thanks for the ping, this prototype looks more like a one piece design already. Iniquity (talk) 10:15, 15 March 2023 (UTC)
 * This would be greatly appreciated. While I would personally prefer the frameless variant, either prototype variant helps bring Wikipedia back in line with WCAG supplemental guidance - specifically Make the Site Hierarchy Easy to Understand and Navigate and Use a Clear and Understandable Structure. The table of contents, while still available as a useful navigational aid, is differentiated from the page itself through more than just a bit of whitespace and is rightly no longer treated as if it is equally important to focus on as the page content. While this will not be as easy to read and navigate as the old skin - hierarchy could still use work, mostly with regard to menu structure - it will be a major improvement accessibility-wise (at least for me) compared to currently existing Vector 2022.
 * One suggestion: for any testing, please keep the goals of this change in mind, not just the overall goals for the project. Decreased use of the table of contents compared to current Vector 2022 may well be something you'll have to live with for accessibility; making it less obtrusive and easier to not focus on is rather the point. 24.246.2.244 03:45, 16 March 2023 (UTC)
 * Why does prototype with current look different than current desktop site?
 * At least on my PC it has less "white"(cause it has grey boarders left and right) space than the normal desktop current site.
 * I recognize (too) much white space as highly (aggravating) distracting, so i even like linked current prototype (di-content-separation.web.app) more than actual desktop current, because it is wider.
 * I prefer unframed as i like dark mode more in general but both options are ok. Framed mode shouldn't move any content around so, which the prototype still does.
 * I think (as i have written in another discussion where it got deleted -.-) that the idea of a width limit (especially the current one) to ease reading is fine, but only for text. So taking the moss site as an example, i would suggest using whites pace on the right for things like this overview card and pictures, as well as for things like the tool toolbar. For now pinning the toolbar moves the whole content instead of it just being put into white space (which is wide enough for it).
 * Another option still would be to have the maxed setting as default, which honestly looks the best so far for me, but it obviously makes it a bit harder to read, but doesn't anger me because of too much white space.
 * This is all on a 1920px and a second 1680px width screen in maximized browser mode.
 * Now when i partition it and use half a screen which is pretty nice to use 2 files (like an opened pdf and a text file) the prototype compared to desktop current is more narrow both with current or Zebra #9 settings, which it does not need to be. Hope it will get better with the newer margins.
 * So overall i'm a) confused why current prototype(di-content-separation.web.app) is different than current desktop, b) i like the idea of darker areas (which makes big white spaces more bearable) and i still would prefer a bigger width limit which truly reduce white space and not just visually makes it more bearable. Pinned Tools should also be put into white space if it is big enough and not shrinking the actual content and still leaving white space on the right which now has 0 validity, as the toolbox itself is not longer than current max width.
 * Limited max width makes sense for each single element you need to recognizance but not a combination of multiple elements like a separate toolbar.
 * I still would hope to see a general ("sentiment") survey for all wiki users (majority is probably not logged in or even registered) between designs.
 * In this regard i think it is pretty important to give any kind of participants in studies the option between different (st least 2) designs. Telling someone if Option A or B is "better"(relative comparison?), is a lot more easy to do than rating how good one Option is. YaphitsBrother (talk) 11:03, 17 March 2023 (UTC)

If you ask me, please go ahead both with developing and testing, as laid out above. Regards Aschmidt (talk) 06:32, 9 March 2023 (UTC)


 * +1 Aschmidt. The proposed prototype seems better than the current layout. Jules* (talk) 09:42, 9 March 2023 (UTC)
 * Personally, I like the grey background because it is much easier to tell apart the page content from the rest of the wiki. However, pinning the tools menu reduces the width even more, and this is not a good thing, as the unlogged-in readers do not have the tools menu pinned, and as such, the width seen by the editor would be different than the width seen by the reader. -- NGC 54  ( talk |  contribs ) 11:42, 9 March 2023 (UTC)
 * @NGC 54 the users will most likely be using mobile device 😉 (above 60%) Nux (talk) 01:47, 10 March 2023 (UTC)
 * This is simply not relevant. There are a lot of people who read Wikipedia on desktop, and ensuring a good layout for desktop is important. -- NGC 54  ( talk |  contribs ) 12:53, 10 March 2023 (UTC)
 * @NGC 54 this is relevant and in fact very important. Even on desktop there are many resolutions out there. On a 13 inch laptop/netbook (e.g. in school) your experience will be completely different then on 15 inch laptop (gaming/work laptop) and different on 22.5 inch monitor (as my own). You should always design content so that it can be useful in different resolutions, it might seem hard, but it mostly just works on Wikipedia (unless you use weird templates or too specific html). If you don't know the term RWD, you might want to read about Responsive web design. In fact, in practice, you should never design a page for a specific width. Nux (talk) 19:39, 10 March 2023 (UTC)
 * +1 hgzh 08:48, 28 March 2023 (UTC)

I like the gray background and borders, which of course exists here on the MediaWiki site (I guess I am still using Vector 2010 here) and are very helpful. The fundamental problems of excessive white space and padding are still present (for me) on that Moss demo page, however. My browser window is 1228 pixels wide; on en.WP in Vector 2022, I have managed to remove a lot of the whitespace and end up with 835 pixels of usable width for content with the TOC and Tools menu pinned to the side. On my screen, the demo Moss page has only 635 pixels of horizontal space for content, which feels very constrained. Many display elements like tables and multiple columns that work now will either overflow, scroll, or be single columns in this new layout. Image "sandwiching" will be a significant problem, and there will be editing disputes about modifying pages to accommodate this overly narrow width (editors using larger monitors or skins with reasonable padding will not see a problem and will object to the wikitext changes).

Since the rollout of Vector 2022 to all readers, I have submitted many bug reports about excessive whitespace and padding. A few of them have been fixed, but there is much more work to do.

One other thing: If I pin the TOC and the Tools menu on the demo Moss page, and then shrink the window horizontally, the TOC responsively collapses into a button, but the Tools menu persists, shrinking the content column. I suspect that this is not the desired behavior. Jonesey95 (talk) 14:51, 9 March 2023 (UTC)

I didn't mind the all-white-bg design (loved it!), but if we're gonna have gray sides, better make the menus frameless. Too many misaligned framed boxes look&feel messy. Add sitenotice boxes (weird positioning! anyone thought of that?), infoboxes, image boxes, each of their own widths and the whole page is painful to look at. Also, page elements (boxes) should not jump as toolbars on the left or right are added, especially so when switching between namespaces. Reserve enough margin on the left and right for those menus and have the central (article) panel neatly centered. I loved and supported the new skin from the start, but this has turned into a jumping mess. Still using V2022 as I've not lost all hope, but it's an everyday hide/show/pin NS0/NS>0 struggle (I like to keep the main menu closed for articles, so the TOC is on top of the page, but as a sysop I want the menu, thus shorter text lines in other namespaces and on special pages). And, oh, did I mention ~double line spacing in those menus – why should one need to scroll the page to reach the bottom of a 15-item list? p o nor    (talk) 15:59, 23 March 2023 (UTC)
 * Strong oppose any borders, visual separation, etc (all of the Zebra prototypes). EpicPupper (talk) 23:28, 23 March 2023 (UTC)


 * A definite improvement, thanks and keep it up. Still too much whitespace: between the header and the top of the body; between the outer edge of the menus and the edge of the page (the open/close caret could line up with the burger-menu icon, rather than the latter lining up w/ the edge of the box); the main menu is much too wide; the tools menu could be slightly less wide. Still confusing font/kerning choices: It would be better to keep menu text smaller, and line height proportionally smaller, and to lightly bold the menu section-headings. That saves space, reduces scrollsing, avoids confusion with body text, and helps the eye more easily peruse a long menu. Sj (talk) 21:31, 28 March 2023 (UTC)

Hi everyone, Thank you all so much for your feedback on the prototype and proposed measurement plan. Based on this feedback, we will proceed as follows:


 * 1) User testing: we will set up user testing with readers.  In this testing, participants will be presented with either the current layout or the proposed layout and encouraged to explore an article with both layouts and interact with the different menus.  Afterwards, participants will be asked questions about their experience.  The goals of the test will be:
 * 2) Understand if the visual separation makes it easier for users to focus on content.
 * 3) Understand if the visual separation makes for a more comfortable reading experience.
 * 4) Understand if the visual separation makes it easier for people to navigate the article.
 * 5) Identify any potential improvements that could be made to enhance the reading experience.
 * 6) Gauge user preferences between current Vector 2022 and the new prototype.
 * 7) A/B testing: We also want to ensure that the new layout does not negatively affect any current high-level metrics for the project, which will be determined via an A/B test.  Due to privacy and technical restrictions, we are only able to run this test with logged-in users.    We will be able to filter the results by the number of edits a given user has, and can potentially proxy logged-out users via logged-in users with 0 edits.  We will be looking for no statistically significant decreases in the following:
 * 8) Pageviews
 * 9) Edit rate
 * 10) ToC usage
 * 11) Scrolling
 * 12) Page tools usage
 * 13) Feature review: A few of you have mentioned that there are some layout inconsistencies in the prototype related to spacing and alignment.  We are currently reviewing these and will update with any changes.

Thank you all once again. We’re looking forward to your thoughts on this updated measurement plan. We plan on starting the user testing portion later this week, and the A/B testing portion within a couple of weeks. For those interested in tracking progress in phabricator, most of the work is tracked as subtasks of this ticket. OVasileva (WMF) (talk) 16:48, 29 March 2023 (UTC)


 * @OVasileva (WMF), aesthetically, I think I could come to like the gray. The screen width would certainly be a tradeoff, though, given that there were already concerns about it being too narrow.
 * You wrote It increases the width of the content when the page tools menu is closed, when compared to the current width, which is not what I'm seeing in the prototype. It looks to me like the width for the gray design with page tools closed is narrower than for the white design with page tools closed. Could you clarify on that? The appearance with page tools closed is what I care most about, since virtually all readers (and many editors, including myself) are going to prefer that.
 * One way to create more space might be to not have a border to the left of the table of contents. I'm curious what that would look like. Cheers, &#123;{u&#124; Sdkb  }&#125;  talk 15:49, 4 April 2023 (UTC)
 * I really prefer the current deployed version over the prototype. The separation wastes quite a lot of space, and the gray+white combo looks strangely formal compared to the plain white version. DFlhb (talk) 17:58, 8 April 2023 (UTC)

Access to right side toolbar
When scrolled down the page with the left side toolbar hidden, it becomes impossible to set to show without going back to the top menu as the tools menu is not in the sticky header. This is annoying and a bit of a time-waster.

Also, the right sidebar is wastefully wide and the scroll bar is inset unnecessarily far from the page edge. Due to vision problems I often zoom in a bit to make the body text more legible while editing and with the side by side preview I cannot afford the wasted space on the right.

I really like the live-ish preview, but it should show what I have last edited, not require me to scroll around in what can be a very large piece of content until I find it or use the page search function. Try editing a references section with about 200 list formatted references to see what I mean. Cheers, Pbsouthwood (talk) 09:38, 14 March 2023 (UTC)
 * Hello @Pbsouthwood. I've taken the liberty to split your comment into three different paragraphs. Would you agree with how I've done that?
 * Regarding the first part, I think the simplest follow-up is – what prevents you from pinning the menu when you're about to use it more often, and unpinning it when you need to have a wide view to enjoy the Real Time Preview? What practical disadvantages does this method have in your case?
 * Regarding the second part, could you share a screenshot with too wide areas marked? This will help us understand what you see. Thank you!
 * SGrabarczuk (WMF) (talk) 17:01, 30 March 2023 (UTC)

Новый прототип. Визуальные различия между интерфейсами
Всем привет,

Мы проанализировали ваши отзывы о макете страницы. Мы ознакомились комментариями, которыми вы поделились здесь, а также на RfC (страница для комментариев) в Английской Википедии, на форуме, на других страницах Вики, в Фабрикаторе, а также на встречах. Вот обновления по этой работе. Мы хотели начать дискуссию о следующих шагах по дальнейшему улучшению макета.

Отзывы о пустом пространстве

На данный момент «Векторная 2022» использует пустые пространства для разделения различных областей интерфейса. Оно также имеет белый фон страницы (за пределами области контента). В связи с этим есть две области, вызывающие вопросы:


 * 1) Комментарии насчёт добавления дополнительного визуального различия между оюластями интерфейса. Вам было интересно, улучшит ли это процесс чтения. Главным образом, за счёт:
 * 2) * Привлечения большего внимания/фокуса к контенту при переходе на страницу (вместо того, чтобы сначала рассматривать интерфейс в целом, а затем сфокусироваться на контент).
 * 3) * Чтобы было легче сосредоточиться на контенте во время чтения, поскольку область контента была бы более чётко определена (некоторые из вас сообщали, что отвлекались на содержание во время чтения)
 * 4) Комментарии по поводу добавления серого фона за пределами области контента. Вам было интересно, уменьшит ли это нагрузку на глаза, которую испытывают некоторые люди из-за большой пустой области на больших экранах.
 * 5) * Многие из вас сообщали, что пустое пространство слишком контрастно и что добавление более темного оттенка, такого как серый, уменьшает это нагрузку.

Прототип – предлагаемые изменения и компромиссы Основываясь на этом, а также на отзывах о дальнейших итерациях, мы подготовили этот прототип. (T259240) Это предложение о потенциальных изменениях. Прототип основывается на:


 * 1) Добавление границ как вокруг области контента, так и вокруг содержания (а также других меню). Наша гипотеза заключается в том, что эта грань может помочь в дальнейшем структурировании и уточнении интерфейса. Это также облегчило бы фокус на контенте (как при первой загрузке страницы, так и во время чтения). Обратите внимание, что вы можете закрепить меню «Инструменты», используя выпадающий список справа.
 * 2) Сделать задний фон страницы серым. Наша гипотеза заключается в том, что это должно помочь уменьшить напряжение на глаза, которое испытывают некоторые люди. Это также придало бы дополнительный акцент области контента и содержания.

Мы изучаем конфигурацию, которая будет включать в себя белый фон заглавления, границы, а также меню в рамке.

Но это сопряжено с некоторыми компромиссами. Эта конфигурация влияет на ширину контента. Конкретно:


 * Это уменьшает ширину контента по сравнению с текущей версией в случае, когда меню инструментов страницы (справа на скриншоте) открыто.
 * Это увеличивает ширину контента при закрытом меню «Инструменты страницы» по сравнению с текущей шириной.

Тестирование

В качестве следующего шага мы хотели бы предложить вам эксперимент или серию экспериментов, которые могут подтвердить вышеприведённые наши гипотезы. Мы стремимся определить, улучшит ли обновление макета таким образом впечатления на читателей и редакторов. У нас есть несколько различных вариантов для этого. На данный момент мы рассматриваем следующее:


 * 1) Качественное тестирование — провести тестирование пользователей с помощью интервью с читателями и редакторами. Это будет направлено на то, чтобы приблизительно определить, легче ли сосредоточиться на контенте и снижает ли новый фон нагрузку на глаза
 * 2) A/B тестирование — запустить A/B тест для вошедших в систему пользователей, который проверяет ключевые показатели проекта, сравнивая текущий макет с предыдущим макетом. В частности: количество отказов, просмотры страниц, правки, продолжительность сеанса, использование содержания и прокрутка. Из-за наших технических ограничений и соображений конфиденциальности мы не можем выполнять A/B тестирование для вышедших из системы пользователей. Это означает, что мы будем использовать поведение для вошедших в систему пользователей в качестве прокси для всех пользователей. Если выбран новый макет, мы сравним ключевые показатели (до и после изменения) у всех пользователей.

Некоторые из вас предложили создание опроса, в котором пользователей спрашивают о том, какой интерфейс они предпочитают. Опросы могут быть полезны, но мы не думаем, что они являются лучшим инструментом для оценки удобства использования. Причина этого в том, что мы не думаем, что этот тип опроса даст нам информацию, необходимую для подтверждения или опровержения двух основных гипотез, приведенных выше.

Наши вопросы для вас

Нам интересно, подходит ли привёденный выше список для оценки функций. Если нет — есть ли у вас какие-либо другие идеи по оценке? Мы ищем идеи по измерению того, помогает ли новый макет различию контента и снижает ли нагрузку на глаза.

Помимо оценки, упомянутой выше, мнения наших сообществ также играют большую роль в определении того, какие изменения являются наилучшими. Что вы все думаете о новом прототипе?

Мы пригласим больше добровольцев и сообществ к этому обсуждению. Мы хотели бы пригласить некоторых из вас, представляющих разные сообщества, в качестве первой группы заинтересованных редакторов:

Kaganer, MBH, Vladimir Solovjev, Abiyoyo, Deinocheirus, VladimirPF, Putnik, DR, Stjn, Q-bit array, DonRumata, Jack who built the house, Adamant.pwn, Alex Spade, AndyVolykhov, Bezik, Ghuron, Джекалоп, Ле Лой, Сайга.

Спасибо — Mehman (WMF) (talk) 21:36, 16 March 2023 (UTC)
 * @Mehman, пинг не прошёл (не знаю почему). MBH (talk) 22:26, 17 March 2023 (UTC)
 * Спасибо, что сообщил, попробую по-другому – Mehman (WMF) (talk) 07:49, 18 March 2023 (UTC)


 * Не увидел разницы. Пришлось изучить скриншот в гимпе, чтобы обнаружить бледно-серые границы. Вариант с серым заполнением полей был удачнее. Что же до сомнений в "уменьшает ширину" - помилуйте, даже в вашем скриншоте слева и справа от колонок с меню по целой ладони белого поля. Сдвиньте колонки меню к краям экрана, вот и место для текста освободится. Retired electrician (talk) 08:04, 21 March 2023 (UTC)
 * (In English for simplicity) As I’ve said many times before, I would prefer frameless menu because this is a more visually appealing design (no opinion on header because it’s not as distracting/concerning). Thankfully, most of the people who have commented here seem to agree. Not sure if this will make the new Vector team to proceed in the better direction, though, since framed menus were, from our discussions, by the insistence of AHollender. stjn[ru] 23:18, 2 April 2023 (UTC)

Tagline issue
On Romanian language Wikipedia, the tagline („De la Wikipedia, enciclopedia liberă”) is a little misaligned. Compare ro:Zebră with en:Zebra. -- NGC 54  ( talk |  contribs ) 16:05, 17 March 2023 (UTC)


 * Hello @NGC 54. I think we have talked about this before, but can't quite remember the conclusions. Because I know you're skilled technically, I'd like to double-check before I ask the engineers for their attention – are you sure this isn't a local matter that could be solved on the community side? SGrabarczuk (WMF) (talk) 15:54, 30 March 2023 (UTC)
 * I do not know how to solve the issue, so I have opened a local discussion: ro:Wikipedia:Cafenea. -- NGC 54  ( talk |  contribs ) 17:02, 3 April 2023 (UTC)

Can't see annotations
My friends told me to look at commons:Category:Images with annotations but I couldn't see any hint of them with this skin. Jidanni (talk) 22:57, 17 March 2023 (UTC)


 * Hi @Jidanni, thanks for your feedback, I can't reproduce it (for exemple, here annotations appear on hover). Can you give us more detail (browser, OS, screen resolution) please? Patafisik (WMF) (talk) 09:05, 20 March 2023 (UTC)

Timeline - Finnish Wikipedia?
The Finnish WP is mentioned in the timeline for discussions in January, but no discussion has yet been had there. Are there plans on when it might be happening in the Finnish WP? There have been a couple of discussions among users about the new layout, and I'd be interested to know if the "official" discussion is coming (or not coming) any time soon. kyykaarme (talk) 13:06, 19 March 2023 (UTC)


 * Hello @Kyykaarme. Thank you for coming here and asking this! At the moment, we don't have any strict plans. I've subscribed to the discussion Vector 2022 -ulkoasun käyttöönotto?, though, and I'll post a message there! SGrabarczuk (WMF) (talk) 14:48, 21 March 2023 (UTC)

External Link Colors
Could you respond to my proposal for external link colors made in a comment in the Wikipedia RFC thread? If the proposal is doable can we implement it? If not, why not and what solution would you suggest for addressing the lack of distinction between internal and external links that the Vector 2022 link color change has caused? (The reasons for the need for this distinction are explained in another comment.)

My understanding, based on an earlier post in this thread I came across that linked to a blog post that explains the problem, is that the WCAG 2.0 AA requirements are so excessively strict that they leave a very limited amount of colors that can be used. However, while less than ideal, if we insist on meeting the AA standard, the same blog post links to a few other options that we can use. –Noha307 (talk) 18:44, 19 March 2023 (UTC)
 * Hello @Noha307. Thanks for coming to us with this issue. I've asked my team mates to document our decisions. Hopefully it will be clarified. SGrabarczuk (WMF) (talk) 15:51, 30 March 2023 (UTC)
 * Thanks for following up on this. I particularly appreciate the effort to document decisions. The WCAG standards are complicated – both in terms of the multiple levels of compliance (e.g. A, AA, AAA) and the different standards for different types of text (e.g. link text versus body text color and body text versus background color) – so trying to parse them out was confusing. The Link Colors section on the Visual Refinements page does not mention any of the standards by name and only internal link colors are discussed, so it was difficult to determine what the self-imposed requirements were.
 * Also, I realized the wording of my comment and use of multiple pings might have seemed a bit aggressive, so I apologize if it appears that way. –Noha307 (talk) 16:47, 31 March 2023 (UTC)

Nuevo prototipo. Separación visual entre áreas
Hola,

Hemos analizado los mensajes que nos habéis hecho llegar sobre el diseño de la página aquí, así como en el RfC (Request for comments) en la Wikipedia en inglés, los Cafés o Village Pumps, otras páginas wiki, Phabricator, así como en reuniones. A continuación, compartimos nuestras actualizaciones sobre este trabajo. Nos gustaría iniciar una conversación sobre los próximos pasos para seguir mejorando el diseño.

Opiniones sobre el espacio blanco

En la actualidad, Vector 2022 utiliza espacio blanco para separar las diferentes regiones de la interfaz. También tiene un fondo de página blanco (fuera del área de contenido). Hay dos cuestiones acerca de esto:


 * 1) Comentarios sobre añadir más separación visual entre regiones de la interfaz. Se ha preguntado si esto mejoraría la experiencia de lectura. Principalmente por:
 * 2) * Centrar más la atención en el contenido al entrar en la página (en lugar de ver primero la interfaz en su conjunto y luego centrarse en el contenido).
 * 3) * Facilitaría la concentración en el contenido mientras se lee, ya que el área de contenido estaría mejor definida (algunas personas han informado de que se distraen con el índice de contenidos mientras leen).
 * 4) Comentarios sobre añadir un fondo gris fuera del área de contenido. Se ha preguntado si esto reduciría la fatiga visual que algunas personas están experimentando debido a la gran área blanca (es decir, deslumbramiento) en pantallas más grandes.
 * 5) * Muchas personas han informado de que el espacio en blanco tiene un contraste demasiado alto y que añadir un tono más oscuro, como un gris, disminuiría esta tensión.

Prototipo - cambios propuestos y alternativas Basándonos en esto, así como en los comentarios sobre iteraciones posteriores, hemos preparado este prototipo. (T259240) Se trata de una propuesta de posibles cambios. El prototipo se centra en:


 * 1) Añadir un marco alrededor del área de contenido y del índice (así como de otros menús). Nuestra hipótesis es que este marco puede ayudar a estructurar y clarificar la interfaz. También haría más fácil centrarse en el contenido (tanto cuando la página se carga por primera vez, como durante la lectura). Ten en cuenta que puedes fijar el menú Herramientas utilizando el desplegable de la derecha.
 * 2) Hacer que el fondo de la página sea gris. Nuestra hipótesis es que esto debería ayudar a reducir la fatiga visual que algunas personas están experimentando. También añadiría más atención al área de contenido y a la tabla de contenidos.

Nos inclinamos por la configuración que incluye el fondo blanco de la cabecera, los bordes y los menús enmarcados.

Pero esto tiene algunas desventajas. Esta configuración afecta a la anchura del contenido. Específicamente:


 * Reduce el ancho del contenido en comparación con la versión actual en el caso de que el menú de herramientas de página (el de la derecha en la captura de pantalla) esté abierto.
 * "Aumenta el ancho'' del contenido cuando el menú de herramientas de página está cerrado, en comparación con el ancho actual.

Nuestro equipo de diseño está trabajando para limitar sus efectos. Están ajustando parte del relleno y los márgenes, lo que se reflejará en el prototipo en los próximos días.

Testing

Como siguiente paso, nos gustaría proponer un experimento o una serie de experimentos que puedan validar las hipótesis anteriores. Nuestro objetivo es determinar si esta actualización del diseño mejoraría la experiencia de lectura y edición. Tenemos un par de opciones diferentes para ello. Por ahora, estamos considerando las siguientes:


 * 1) Pruebas A/B: realizar una prueba A/B con usuarios registrados que analice las métricas clave del proyecto, comparando el diseño actual con el anterior. En concreto: tasas de abandono, páginas vistas, ediciones, duración de la sesión, uso del índice y desplazamiento. Debido a nuestras restricciones técnicas y a cuestiones de privacidad, no podemos realizar pruebas A/B con personas que hayan cerrado la sesión. Esto significa que utilizaremos el comportamiento de quienes hayan iniciado sesión como aproximación para el resto las personas usuarias. Si se selecciona el nuevo diseño, compararemos las métricas clave (antes y después del cambio) entre todos los usuarios.

Hay quienes han mencionado la elaboración de una encuesta en la que se pregunte a las personas qué diseño prefieren. Las encuestas de sentimiento pueden ser útiles, pero no creemos que sean la mejor herramienta para evaluar la usabilidad. La razón es que no creemos que este tipo de encuesta nos proporcione la información que necesitamos para confirmar o rechazar las dos hipótesis principales anteriores.

Nuestras preguntas para ti

Tenemos curiosidad por saber si lo que hemos enumerado más arriba te parece adecuado para la evaluación de las características. Si no es así, ¿tienes alguna otra idea para la evaluación? Estamos buscando ideas para medir si el nuevo diseño ayuda en la separación de contenidos o la fatiga visual.

Además de la evaluación mencionada, las opiniones de nuestras comunidades también desempeñan un papel importante a la hora de decidir qué cambios son los mejores. ¿Qué os parece el prototipo?

Muchas gracias por vuestra colaboración. Saludos. Zapipedia (WMF) (talk) 00:52, 20 March 2023 (UTC)


 * Gracias por escuchar los comentarios y proponer este nuevo prototipo. Desde mi perspectiva, enmarcar el contenido y añadir un fondo gris mejora bastante los problemas que genera la nueva interfaz. Sin embargo, me parece que el diseño sería más limpio si solo el contenido (columna central) estuviera enmarcado; los menús deberían permanecer con fondo gris, tal como se puede visualizar en el prototipo desmarcando la opción framed menus.
 * De igual manera, me parece que la tabla de contenidos debería permanecer fija en la columna izquierda. Al seleccionar hide, la tabla de contenidos se oculta en una posición poco intuitiva; volverla a su lugar requiere encontrar el botón, y hacer dos clics consecutivos, lo cual me parece un esfuerzo absurdo considerando que ocultarla no aporta ventaja alguna. En caso de mantener la opción de ocultar la tabla de contenidos, por favor consideren reemplazar el enlace [ocultar] (con corchetes) por una flecha u otro ícono.
 * Finalmente, me parece que los menús desplegables estilo pop-up son inconsistentes con la estética minimalista propuesta. Particularmente el menú principal impresiona que está sobrando, porque no queda bien ni como pop-up ni fijo en la barra lateral, desplazando a la tabla de contenidos. Una posible solución sería desplegar los enlaces (Portal de la comunidad, Actualidad, etc.) de forma horizontal entre la cabecera y el contenido al hacer clic en el botón de sándwich, y permitir ocultarlos con el mismo botón. DEGA MD (talk) 04:04, 1 April 2023 (UTC)

Un nuovo prototipo: separazione grafica tra le aree
Ciao,

abbiamo analizzanto il feedback che ci avete dato sul layout della pagina. Abbiamo letto sia i commenti che ci avete lasciato qui che quelli nella Request for Comments (RFC) sulla Wikipedia in inglese, nei bar e nelle pagine di discussione, in altre pagine wiki, su Phabricator, o ancora durante i nostri incontri on line. Ecco il nostro aggiornamento sul lavoro svolto. Ci piacerebbe iniziare una conversazione sui prossimi passi da fare per migliorare ulteriormente il layout.

Feedback relativo allo spazio bianco

Attualmente Vector 2022 usa lo spazio bianco per separare le varie aree dell'interfaccia. Ha anche uno sfondo della pagina bianco (al di fuori dell'area del contenuto). Ci sono due aspetti che destano perplessità:


 * 1) Commenti relativi all'evidenziare maggiormente la separazione grafica tra le aree dell'interfaccia. Vi siete chiesti se questo migliorerebbe l'esperienza di lettura. Principalmente:
 * 2) * Permettendo di focalizzare l'attenzione/dando maggiore risalto al contenuto fin da subito, quando si arriva sulla pagina (anziché focalizzarsi sull'interfaccia nel suo insieme, e poi sul contenuto)
 * 3) * Rendendo più facile concentrarsi sul contenuto mentre si legge, perché l'area del contenuto sarebbe meglio definita (alcuni di voi hanno riportato che l'indice li distraeva durante la lettura)
 * 4) Commenti relativi all'aggiungere uno sfondo grigio al di fuori dell'area del contenuto. Vi siete chiesti se questo ridurrebbe il senso di affaticamento della vista che alcuni utenti sperimentano per via della grande area bianca (tipo “abbagliamento”) su un monitor grande.
 * 5) * Molti di voi hanno riportato che lo spazio bianco è troppo contrastato e che l'aggiunta di una tonalità più scura come il grigio diminuirebbe questo affaticamento.

Prototipo – cambiamenti proposti e compromessi Sulla base di questo e del feedback sulle iterazioni successive, abbiamo preparato questo prototipo. (T259240) Questa è una proposta per dei potenziali cambiamenti. Il prototipo si focalizza su:


 * 1) L'aggiunta di una linea di demarcazione sia intorno all'area del contenuto che intorno al sommario (e agli altri menu). La nostra ipotesi è che questo limite grafico possa aiutare a strutturare e chiarire ulteriormente l'interfaccia. Renderebbe anche più facile concentrarsi sul contenuto (sia quando si carica la pagina che durante la lettura). Tieni conto che puoi fissare il menu degli Strumenti della pagina utilizzando il menu a tendina sulla destra.
 * 2) Rendere grigio lo sfondo della pagina. La nostra ipotesi è che questo possa andare incontro alle esigenze di chi sta provando un affaticamento oculare. Inoltre ci si focalizzerebbe maggiormente sull'area del contenuto e dell'indice.

Noi propendiamo per la configurazione che comprende lo sfondo bianco dell'intestazione, i bordi e i menu incorniciati.

Ma questa scelta richiede di accettare alcuni compromessi. Questa configurazione ha delle ripercussioni sulla larghezza del contenuto. Nello specifico:


 * riduce la larghezza del contenuto rispetto alla versione attuale quando il menu degli Strumenti della pagina (quello a destra nello screenshot) è aperto.
 * aumenta la larghezza del contenuto rispetto alla versione attuale quando il menu degli Strumenti della pagina è chiuso.

I nostri designer sono al lavoro per limitare questi effetti. A livello grafico stanno aggiustando alcuni margini esterni e interni (padding) che saranno visibili sul prototipo nei prossimi giorni.

Test

Come passo successivo ci piacerebbe proporre un esperimento o una serie di esperimenti per convalidare le ipotesi di cui sopra. Il nostro proposito è quello di capire se, aggiornando il layout in questo modo, l'esperienza dei lettori e dei contributori sia migliore. Per questo abbiamo pensato a un paio di opzioni. Per il momento, stiamo prendendo in considerazione quanto segue:


 * 1) Test qualitativi – condurre test di usabilità attraverso interviste con lettori e contributori, per valutare se sia più facile concentrarsi sul contenuto e se il nuovo sfondo riduca l'affaticamento oculare.
 * 2) Test A/B – condurre un test A/B sugli utenti loggati, che analizzi le metriche chiave del progetto, confrontando il layout attuale con quello precedente. Nello specifico: i tassi di abbandono  (opt-out), visualizzazioni della pagina, edit, durata della sessione, uso del sommario, e  scorrimento della pagina. A causa di limitazioni tecniche e problemi di privacy, non siamo nelle condizioni di condurre test A/B sugli utenti non connessi. Questo significa che useremo il comportamento degli utenti registrati come indicatore del comportamento di tutti gli utenti. Se il nuovo layout è selezionato, compareremo le metriche chiave (prima e dopo il cambiamento) per tutti gli utenti.

Alcuni di voi hanno menzionato la preparazione di un sondaggio che chieda agli utenti quale layout preferiscano. I sondaggi sul gradimento (sentiment surveys) possono essere utili, ma non riteniamo che siano lo strumento migliore per valutare l'usabilità. Questo perché non riteniamo che questo tipo di sondaggi possa fornirci le informazioni necessarie per confermare o confutare le due ipotesi principali di cui sopra.

Cosa ti stiamo chiedendo

Siamo curiosi di sapere se l'elenco qui sopra ti sembri adeguato per la valutazione delle caratteristiche.

Se la risposta è no – hai un'altra idea da proporre per la valutazione? Stiamo cercando idee per misurare se il nuovo layout aiuti a separare i contenuti o con l'affaticamento oculare.

Oltre alla valutazione di cui sopra, anche le opinioni delle nostre comunità giocano un ruolo fondamentale nel capire quali cambiamenti siano i migliori. Voi cosa ne pensate del prototipo?

Grazie dell'attenzione! OVasileva (WMF), SGrabarczuk (WMF) --Patafisik (WMF) (talk) 09:31, 20 March 2023 (UTC)


 * Notifico in ordine sparso ho dimenticato sicuramente molti utenti interessati o che sono intervenuti in passato nelle discussioni sull'interfaccia, se pensate che a qualche altro wikicollega possa interessare dire la sua invitatelo alla discussione. Il team sta lavorando anche su altri dettagli di Vector 2022, posso aiutarvi a trovare i task esistenti o aprirne di nuovi se vi interessa. Se avete delle domande sono a disposizione. Buona giornata, Patafisik (WMF) (talk) 12:29, 21 March 2023 (UTC)
 * Invito anche a testare il nuovo prototipo e a dare un feedback anche sulla modalità dei test qualitativi e quantitativi. Grazie! Patafisik (WMF) (talk) 11:28, 23 March 2023 (UTC)

Le nouveau prototype : séparation des régions du gabarit
Bonjour à toutes et à tous,

Nous avons analysé vos remarques sur la mise en page. Nous avons lu les commentaires que vous avez partagés ici, ou dans la Requests For Comments (RFC) sur la Wikipédia en anglais, aux Bistros et sur d'autres pages wiki, sur Phabricator ou encore pendant les rencontres en ligne. Ci-dessous notre mise à jour par rapport à ce travail. Nous aimerons entamer une conversation autour des prochaines étapes de l'amélioration de la mise en page.

Retour sur l'espace blanc

Actuellement, Vector 2022 utilise l'espace blanc pour separer les différents éléments du gabarit de l'interface. Le fond de la page de l'habillage s'affiche en blanc (en dehors de la région du contenu). Deux sujets de préoccupation ont émergé par rapport à ceci :


 * 1) Certains commentaires concernaient l'ajout d'une majeure séparation visuelle entre les régions de l'interface. Vous vous êtes demandé si cela améliorerait l'expérience de lecture. Surtout :
 * 2) * en attirant davantage l'attention sur le contenu dès l'arrivée sur la page (plutôt que de considérer l'interface dans son ensemble, pour se concentrer sur le contenu ensuite).
 * 3) * en facilitant la concentration sur le contenu pendant la lecture, puisque la région du contenu serait mieux définie (certains d'entre vous ont signalé que le sommaire les distrayait durant la lecture)
 * 4) D'autres commentaires concernaient l'ajout d'un fond de couleur grise en dehors de la zone de contenu. Vous vous êtes demandé si cela pourrait réduire la fatigue oculaire que certaines personnes ressentent à cause de la grande surface blanche (une sorte d ' éblouissement) sur les écrans de grande taille.
 * 5) * Beaucoup d'entre vous ont signalé que l'espace blanc était trop contrasté, et que l'utilisation d'une teinte plus foncée, comme le gris, diminuait cette tension.

Prototype – changements et solutions de compromis proposés À partir de ces éléments et des commentaires sur les itérations successives, nous avons préparé ce prototype. (T259240) Il s'agit d'une proposition de changements potentiels. Le prototype se focalise sur :


 * 1) L'ajout d'une ligne de démarcation autour de la zone du contenu et du sommaire (ainsi que d'autres menus). Notre hypothèse est que ce contour permettrait de structurer et de clarifier davantage l'interface. Il permettrait également de se concentrer davantage sur le contenu (à la fois lors du chargement initial de la page et pendant la lecture). Notez que vous pouvez épingler le menu Outils à l'aide du menu déroulant sur la droite.
 * 2) Le fond de la page en couleur grise. Notre hypothèse est que cela devrait contribuer à réduire la fatigue oculaire dont souffrent certaines personnes. Cela permettrait également de mettre davantage en évidence la zone de contenu et le sommaire.

Dans ce contexte, nous penchons pour la proposition avec le fond blanc de l'en-tête, les contours et les menus encadrés. Mais cela implique quelques compromis. Cette configuration affecte la largeur du contenu. Notamment :


 * Cela réduit la largeur du contenu par rapport à la version actuelle quand le menu des Outils de la page (celui de droite dans la capture d'écrans) est ouvert.
 * Cela augmente la largeur du contenu par rapport à la largeur actuelle quand le menu est fermé.

Nos designers sont au travail pour limiter ces effets. Ils sont en train d'ajuster certains éléments graphiques tels que les marges intérieures (« padding ») et extérieurs qui seront affichés sur le prototype dans les prochains jours.

Phase de test

Comme étape suivante, nous aimerions proposer une expérience ou une série d'expériences permettant de valider les hypothèses ci-dessus. Nous cherchons à déterminer si une telle mise en page améliorerait l'expérience des lecteurs et des éditeurs. Pour ce faire, nous disposons de plusieurs options. Actuellement, nous envisageons les options suivantes :


 * 1) Tests qualitatifs - effectuer des tests utilisateurs en réalisant des interviews de lecteurs et de rédacteurs. Ces tests viseraient à déterminer si le contenu est plus facile à focaliser et si le nouvel arrière-plan réduit la fatigue oculaire.
 * 2) Tests A/B - effectuer des tests A/B avec les utilisateurs connectés, examiner les indicateurs clés du projet en comparant la mise en page actuelle avec la précédente. Plus précisément : taux de retrait (opt-out rate), pages vues, modifications, durée de la session, utilisation du sommaire et défilement de la page. En raison de nos restrictions techniques et de nos contraintes en matière de protection de la vie privée, nous ne sommes pas en mesure d'effectuer des tests A/B sur les utilisateurs déconnectés. Cela signifie que nous utiliserons le comportement des utilisateurs connectés comme indicateur pour tous les utilisateurs. Si la nouvelle mise en page est choisie, nous comparerons les indicateurs clés (avant et après le changement) pour tous les utilisateurs.

Certains d'entre vous ont mentionné l'élaboration d'une enquête demandant aux utilisateurs quelle mise en page ils préfèrent. Les enquêtes de satisfaction (sentiment surveys) peuvent être utiles, mais nous ne pensons pas qu'elles soient le meilleur outil pour évaluer l'utilisabilité. En effet, nous ne pensons pas que ce type d'enquête nous fournirait les informations dont nous avons besoin pour confirmer ou rejeter les deux principales hypothèses ci-dessus.

Ce que nous vous demandons

Nous sommes curieux de savoir si la liste ci-dessus vous convient pour l'évaluation des caractéristiques. Si ce n'est pas le cas, avez-vous d'autres idées pour l'évaluation ? Nous cherchons des idées pour mesurer la fatigue oculaire ou si la nouvelle mise en page permet de mieux séparer les contenus.

En plus de l'évaluation mentionnée ci-dessus, les opinions de nos communautés jouent également un rôle important dans la détermination des meilleurs changements à apporter. Que pensez-vous du prototype ?

Merci! OVasileva (WMF), SGrabarczuk (WMF) -- Patafisik (WMF) (talk) 10:29, 20 March 2023 (UTC)


 * Bonjour,
 * Personnellement, j'apprécie beaucoup la séparation des régions et le fond contrasté : on n'a plus ce sentiment de "fourre-tout" où l'on ne distingue pas bien ce qui concerne l'article et ce qui est plus général.
 * Merci pour ces changements ! Daehan (talk) 10:59, 21 March 2023 (UTC)
 * +1. Jules* (talk) 11:13, 21 March 2023 (UTC)
 * +1. Reptilien.19831209BE1 (talk) 16:00, 21 March 2023 (UTC)
 * +1 Pas mal du tout ! Thomas³ (talk) 04:37, 22 March 2023 (UTC)
 * +1 Cela met effectivement en lumière les limites des différentes zones de la page et est appréciable. Epok (talk) 06:38, 22 March 2023 (UTC)
 * @Patafisik (WMF) Pas mal en effet, mais pourquoi n'y a-t-il plus d'entête fixe ? Est-ce uniquement dû au prototype ? Ayack (talk) 11:04, 22 March 2023 (UTC)
 * @Ayack tout à fait, l'entête fixe est voué à être présent dans l'habillage. Patafisik (WMF) (talk) 16:00, 22 March 2023 (UTC) P.S. Sur le même prototype, on peut se connecter et il apparaît. Pour plus d'information voir la page dédiée.--Patafisik (WMF) (talk) 08:40, 23 March 2023 (UTC)

Reference columns
Forgive me if this has been discussed. I did look!

I just noticed that the new skin seems to force references set to be in two columns into one. See the references at the foot of en:Don Bradman. Is this deliberate? If so, I can't understand why it's considered a good idea. --Dweller (talk) 15:03, 22 March 2023 (UTC)


 * Hello @Dweller. Thanks for coming here with your question. I think what you're referring to is a consequence of Vector 2022 having different width settings than legacy Vector. With V22, by pinning or unpining side menus, you may choose between one, two, and three columns, and the content area is only one of them. If the width of your screen is below a certain threshold, the content area gets narrower because the columns on both sides don't. So even though above some threshold, there are two columns of references, below it, there may be one. Is this helpful? SGrabarczuk (WMF) (talk) 14:08, 23 March 2023 (UTC)
 * I have discussed something similar regarding w:Template:Reflist not displaying in columns when it should, and was told to change my browser zoom from 100% to 90%. As a temporary measure, this fixed my display problem. I have been having issues with the triple-bar hidden menu in the top-left corner being horizontally squished, locked in place, and entirely unusable. As an option, you could try going to your Preferences and switching back to the Vector Legacy skin. &#8212;&#160;CJDOS,&#160;Sheridan,&#160;OR&#160;(talk) 03:41, 7 April 2023 (UTC)
 * Hi @Dweller, I'm doing some tests about your concern. Are you experiencing this on desktop/laptop? In the article of your example (en:Don Bradman) I see more then one column, with open and/or closed menus and with different browsers, don't you? Using and " would be nice. An example where this may be occurring is this discussion, concerning the en-wiki template Template:Compact TOC's use of  which has consensus (developed while Vector 2010 was the default), but with the advent of Vector 2022 results in the suppression of the ToC from the left sidebar, which is an undesirable result according to one user. (Note: regardless whether it is determined that this example is or isn't something directly related to changes in ToC handling by Vector 2022, I'm sure there will be other examples where a testable property would be helpful.) Mathglot (talk) 06:55, 25 March 2023 (UTC)  updated by Mathglot (talk) 20:57, 26 March 2023 (UTC)


 * Hi @Mathglot, thank you for your feedback, a discussion is going on Phabricator about the table of content and magic words, feel free to add any further comments that would be helpful here. Patafisik (WMF) (talk) 14:44, 20 April 2023 (UTC)

I think navigating would be better if TOC and tools positions were swapped
This way, the position would be similar to the old version, and it's the one most people commonly associate with Wikipedia. It also allows to better research the way the encyclopedia works and find new topics, both necessary steps to understand how the project works, how most thing people find on the page are human-made or human-conducted, and it's in general more trasparent on how Wikipedia works and what guarantes and accuracy it can give 37.103.218.189 19:57, 26 March 2023 (UTC)


 * Hi, thank you for your feedback. The Page tools menu has been moved to the right side intentionally, for splitting the sidebar into two menus and making it easier to distinguish which tools are for the individual page and which are for the entire website. Moving the page tools to the far side of the page, now they are near the other page tools (History, Edit, Move, etc.). More details here. Patafisik (WMF) (talk) 14:51, 20 April 2023 (UTC)

Sommaire replié par défaut
Bonjour, y a-t-il un moyen d'avoir le sommaire replié par défaut ? Reptilien.19831209BE1 (talk) 05:38, 30 March 2023 (UTC)


 * Bonjour @Reptilien.19831209BE1, je voudrais être sûre de bien comprendre votre commentaire. Aimerez-vous le sommaire masqué sous l'icône [[file:OOjs UI icon listBullet-ltr.svg|link=]] par défault ? ou au contraire le sommaire présent sur la gauche mais avec toutes les sections cachées ? ou les sections présentes, mais avec les sous-sections fermées par défault ? Pouvez-vous m'en dire plus, sur votre motivation aussi ? Dans le premier cas, je vous informe que vous pouvez réplier le sommaire une seule fois et le masquage sera persistant d'une page à l'autre durant la navigation. Cordialement, Patafisik (WMF) (talk) 10:19, 31 March 2023 (UTC)
 * Une image valant mieux qu'un long discours, voyez celle-ci. Il y a deux pages : à gauche fr:w:Bruce Willis, à droite fr:w:Bruxelles. Pour je ne sais quelle raison, à l'ouverture de ces pages, le sommaire (de l'article) à gauche est ouvert alors que celui de droite est fermé. Je souhaiterais que le sommaire soit toujours replié (comme à droite), peu importe si j'ai déjà visité la page. Comment puis-je faire ? Reptilien.19831209BE1 (talk) 12:50, 1 April 2023 (UTC)
 * @Reptilien.19831209BE1 Merci pour les détails. Je viens d'ouvrir une tâche sur Phabricator, vous pouvez la suivre à ce lien. Au cas où cette solution ne sera pas retenue pour tout le monde, veuillez me notifier à nouveau, nous chercherons une solution individuelle et personnalisée (voir cette section des FAQ). Cordialement, Patafisik (WMF) (talk) 09:12, 3 April 2023 (UTC)
 * Merci @Patafisik (WMF) d'avoir ouvert cette tâche sur Phabricator. Vous avez écrit dans celle-ci « user would like to see sections always closed ». C'est vrai que c'est personnellement ce que je souhaiterais, mais peut-être que d'autres préféreraient que le sommaire soit toujours déplié. À mon avis, c'est quelque chose qui devrait être paramétrable (dans ses paramètres personnels). Je précise ici mais c'est peut-être une information qu'il faudrait faire remonter sur Phabricator, non ? Reptilien.19831209BE1 (talk) 09:32, 3 April 2023 (UTC)
 * @Reptilien.19831209BE1 Modifié. N'hésitez pas à écrire vous même sur Phabricator si vous le souhaitez. L'équipe Web est en train d'explorer comment rendre possible le paramétrage du sommaire, voir T317818. Patafisik (WMF) (talk) 12:47, 3 April 2023 (UTC)

Text selection scrolls rapidly upward
When I select some text that is at the top of the screen the page rapidly scrolls upwards, making me lose control of navigation and I end up selecting a bunch of text. So selecting any text if it is at the top of the screen is damn near impossible, I have to scroll the text toward the middle and then make my selection. I absolutely hate websites that mess with anything to do with scrolling, it makes me dizzy.

On another note I quite like the new design, good job. The toggle limited content width button seems useless though. Hrs70 (talk) 22:22, 31 March 2023 (UTC)


 * Hello @Hrs70. Thanks for coming here. Are you experiencing this on desktop/laptop? By the text that is at the top of the screen you mean page content only, not the interface, right? SGrabarczuk (WMF) (talk) 23:23, 31 March 2023 (UTC)
 * Yeah I just mean the text in some article. Say I have scrolled to the middle of some article, then selecting the text at either of the first 4 lines of text causes the page to scroll rapidly.
 * I went through a bit of debugging and it seems this event listener is being called which causes the scrolling,
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109
 * although  returns immediately the scrolling happens sometime after, seems to be in , but not sure, I don't really have the time to debug this now. EDIT: Forgot to mention, I am running on a desktop PC with linux and Firefox v.109

Hrs70 (talk) 01:08, 1 April 2023 (UTC)

New skin displays incorrectly only when logged in
For some reason—only when I am logged in—article layouts display incorrectly (i.e. text is shoved into a tiny column, and image boxes are broken). However, when I view the same articles when logged out of my Wikipedia account, everything displays as intended. What might the problem be, and how can I fix it?

For reference:



I've tried hiding the menu and tools, but that does not seem to help.

Thanks, Armadillopteryx (talk) 17:29, 6 April 2023 (UTC)


 * Hello @Armadillopteryx. I'll be happy to help you out. Have you tried to add ?safemode=1 to your URL? Does it still happen with this added? SGrabarczuk (WMF) (talk) 19:47, 7 April 2023 (UTC)
 * Thanks for your reply! Adding ?safemode=1 makes the layout even stranger. It makes the infobox larger and pushes all article text to begin after the infobox. Armadillopteryx (talk) 20:23, 10 April 2023 (UTC)
 * Hey @Armadillopteryx. The part about the infobox is expected – it's because ?safemode=1 disables local styles, and it means the infobox will look different. What about the text width below, though? It isn't as narrow as it is without ?safemode=1, I presume? SGrabarczuk (WMF) (talk) 13:58, 11 April 2023 (UTC)
 * Ah, got it. Yes, the text runs the full width of the browser window with ?safemode=1 in the URL. Armadillopteryx (talk) 15:55, 11 April 2023 (UTC)

Vector 2022 vs. Vector Legacy
Regarding the 2022 skin... I don't like it, firmly. Having been using it since it became the default skin, unmodified and without any user scripts, I find that I much prefer the left-side links (article TOC not sharing the same space), user top links, Preference page section tabs, and other things, as they were prior to the 2022 skin. I've been assuming that the 2022 and ongoing changes were implemented to bridge the gap between desktop and mobile viewers, and improve performance on the latest hardware. I had left my skin preference at the default setting after Wikipedia switched to the 2022 skin, because as an editor, I felt it was important to see the same display as logged-out Wikipedia viewers would. The new skin lacks the accessibility and backward compatibility I've come to appreciate, and so I have switched back to the Vector Legacy skin. &#8212;&#160;CJDOS,&#160;Sheridan,&#160;OR&#160;(talk) 03:18, 7 April 2023 (UTC)

The future of Vector 2022 and software decision-making. A meeting with Selena Deckelmann
Let's talk about how the process of deploying and changing Vector 2022 has gone, what the current plan is, and what may be the future of software decision-making!

I'm gonna refer to English Wikipedia, but the topic is universal, really.

For over two weeks, we (the Foundation) and English Wikipedians have been having a discussion about the steps after the closure of the Rollback of Vector 2022 RfC. I think you may be interested in the latest response from our team posted on April 6. We invite you to that discussion, but also to a meeting with Selena Deckelmann, Chief Product & Technology Officer at the Wikimedia Foundation.

We want to hear and talk about
 * Your thoughts around the deployment of Vector 2022 on English Wikipedia and other wikis
 * What the current plan is (we would like to go over our current prototype)
 * What are the options for the future of software decision-making (a discussion about the format of RfCs in this context)

This meeting will take place on Thursday, April 13th at 18:30 UTC on Zoom (click here to join / dial by your location). We look forward to hearing your thoughts and comments. SGrabarczuk (WMF) (talk) 00:40, 8 April 2023 (UTC)

TOC MainPage on sidebar
Hi, there is a way to move the TOC of a main page on the sidebar as all the other pages?

Salv70 (talk) 10:21, 11 April 2023 (UTC)


 * Hello @Salv70. Thanks for asking the question. I'm not sure I understand it, though. What wiki and what main page do you mean? SGrabarczuk (WMF) (talk) 12:45, 11 April 2023 (UTC)
 * Hi @SGrabarczuk (WMF)I'm using mediawiki 1.39 with Vector 2022 template.
 * On all pages of my MediaWiki, the TOC goes to the left sidebar except for the Main Page where it stays on the content page and dosen't even have the hide link. I would like to behave the same way on the main page as well, with the TOC on the left sidebar, is it possible? Salv70 (talk) 16:33, 11 April 2023 (UTC)
 * I have the same question. The TOC isn't even rendering nicely on the Main Page, it has no styling whatsoever. It would be nice to have it render on the sidebar like all other pages, or at least render nicely with the correct styling. Lwangaman (talk) 22:07, 23 April 2023 (UTC)

Interwiki links dependancy from ULS extension.
Hi! I am quite disappointed that interwiki links has dependancy from ULS extension from MW 1.39. ULS extension works not so properly at my wiki farm, that's why I never used it, and basically I don't need it. And it is quite strange that only Vector-2022 skin has this dependancy as other skins displays interwiki language links. Can you explain why developers has done that? Fokebox (talk) 08:21, 18 April 2023 (UTC)


 * Hey @Fokebox. You'll find information about that on the page about the feature. Is this helpful? I understand that there may be some difference between the Wikimedia wikis and third-party wikis. SGrabarczuk (WMF) (talk) 13:46, 18 April 2023 (UTC)
 * Well, let me explain what issues I experience. I begin from the first one:
 * I have different localisations of my wiki farm that has common shared database and common files of mediawiki. All localisations made just like in wikipedia: ru.mywikifarm.org - Russian, en.mywikifarm.org - English, es.mywikifarm.org - Spanish etc. The $wgLanguageCode is determined for every localisation, i.e for English it is $wgLanguageCode = "en";, for $wgLanguageCode = "ru"; is for Russian etc. The issue is that the language of all website is correct for logged in user, but when it is a guest (non logged-in user) all localisations are in Russian, i.e. en.mywikifarm.org - is in Russian, es.mywikifarm.org - is in Russian etc. When I switch off ULS extension then all works fine for logged in user and for guests (non logged-in users). And I don't know how to solve this issue.
 * Fokebox (talk) 19:25, 18 April 2023 (UTC)


 * The second issue is following: When ULS extension is on! I do see the interwiki box showing the number of languages at my Vector-2022 skin, but when I click the box - sometimes the links are shown, and sometimes the box is empty, in spite of that HTML code is fine - I see at HTML this links and text. But it works all strange, sometimes there are links and sometimes there aren't any. And it is difficult to say why it happening and how to debug this.
 * My wiki farm website:
 * MediaWiki 1.39.3
 * PHP 8.0.28 (cgi-fcgi)
 * MySQL 5.7.34
 * Fokebox (talk) 19:45, 18 April 2023 (UTC)

How to disable/hide the switch to old look button?
I like the skin but is there a way to disable/hide the switch to old look button on the sidebar? i dont want my users to be able to do that since it changes a lot of the layout of my wiki AmpereLaw (talk) 15:36, 26 April 2023 (UTC)


 * Hi @AmpereLaw you can read this section of our FAQ. Patafisik (WMF) (talk) 08:54, 28 April 2023 (UTC)

The new look (2022) is terrible.
As a Wikipedian with 17 years of experience, I am unable to work in the new (2022) look. It is unacceptable to me. Fortunately, you can go back to the old look. And so I did. I went back to the "2010" look.. Radek68 (dyskusja)  07:04, 27 April 2023 (UTC)  Radek68  (dyskusja)  07:04, 27 April 2023 (UTC)

Sticky header for anons
I was very surprised today to learn that anonymous users can't see the sticky header in Vector 2022.

The updates, posted by the team in late 2021 and early 2022, included prototypes of the sticky header for both logged-in and logged-out users. The research indicated that it was important for users (from both groups) to be presented with a page title and an option to go to the search. 

What's more, in a study conducted among logged-in users (and thus with strong habits about the page layout), a 15% decrease in the number of page scrolls was observed. It seems reasonable to think that among readers who read more than 1-2 pages, the trend could be repeated. Since the floating header itself has been implemented and deployed, it would seem logical to prepare a version for non-loggers (even if changed only slightly). It's noteworthy to mention that it's typical for various websites to provide a search bar (or at least button to invoke search) not only at the top. People are already accustomed to such a feature. And, as can be found in the Wikimania presentation, there were 30% more search sessions with the new search. 

Even if the header contained only the search engine icon and the page title, it would be a big step forward, in my opinion. And the space on the right could be occupied by the login and account creation buttons (as in the header at the top of the page). I prepared a variant form of the header for logged out:

Reading the news from the Web team, one could get an impression that the implementation of a sticky header for anons was planned (perhaps to be done later than for logged-in). Now that Vector 2022 is the default on many wikis, including many large wikis, and the team is working on visual refinements, the question arises: what happened to the floating header for anonymous users?

In my opinion, not deploying the header for anons deprives them of some of the really good innovations in the new skin. An example would be the search engine, that would available anywhere on the site.

I'd like to hear from the team what's the fate of sticky header for anons. Whether and when can we expect it being deployed? And if not, what was the reason to abandon the idea? Msz2001 (talk) 17:28, 27 April 2023 (UTC)