Reading/Web/Desktop Improvements/Frequently asked questions

When will these changes be available on the largest wikis?
Not in 2020, unless a community volunteers to join our testing. Currently, we are focusing on the development of our first features based on data we have already collected, and on the tests on the early adopter wikis. We do hope to see the changes set as default on all wikis in 2021.

Are the improvements to be implemented on sister projects and on non-Latin script wikis?
Yes. We have already made a list of early adopter wikis which represents various sizes and scripts. We also wanted to ensure that at least one non-Wikipedia project is selected.

Which wikis these changes are available on?
Currently, these are:


 * sister projects:
 * 
 * 


 * non-Latin script wikis:
 * he:
 * fa:


 * Latin script Wikipedias:
 * eu:
 * fr:


 * additionally:
 * [https://office.wikimedia.org/  Office Wiki]

We are open to add more wikis to this list!

How can this be deployed on my wiki?
If you are interested to see the Desktop Improvements as default on your wiki,
 * 1) ask your community and reach the consensus,
 * 2) contact liaison>User:SGrabarczuk (WMF)|SGrabarczuk (WMF), email: sgrabarczuk-ctr@wikimedia.org if you need support.

Will Monobook or Timeless be affected?
No. These changes will be applied to Vector only. [  Vector] has been the default interface on Wikimedia wikis since 2010. No other skins will be affected, including [  Monobook], [  Timeless], [  Minerva] or [  Modern].

Will you improve charts, maps, a-/f-/o-/tmboxes, infoboxes, navboxes, other templates?
No. We will not change anything that's within the light gray article content area (except for the table of contents):

How can I suggest improvements?
Add a section on the [  talk page of the main page of the project] or contact liaison>User:SGrabarczuk (WMF)|SGrabarczuk (WMF), email: sgrabarczuk-ctr@wikimedia.org.

How can I disable it?
It's possible to turn the improvements on and off within prefs>Special:Preferences#mw-prefsection-rendering</>|user preferences. We have also provided an opt-out button in the left sidebar (accessible on each page): [<tvar|optout>https://www.mediawiki.org/w/index.php?title=Special:Preferences&wprov=vctw1#mw-prefsection-rendering-skin-skin-prefs </> ].

How can I report a bug?
You can add a task on Phabricator and add phab>phab:tag/desktop_improvements/</>|Desktop Improvements project tag or contact liaison>User:SGrabarczuk (WMF)</>|SGrabarczuk (WMF), email: sgrabarczuk-ctr@wikimedia.org.

Why not make a new skin?
It would be an excellent idea, but in the case of Wikimedia skins, it's easier to change an existing one than to create a new one from scratch. There are various reasons:
 * it would be too complex to make the existing extensions, gadgets, and user scripts compatible with yet another skin, and too costly to maintain their compatibility,
 * it would be too challenging to build and maintain yet another skin (as a total replacement is not an option),
 * it would be less likely for the communities to collaborate effectively in the process of building a new skin.

Why not use beta features only?
Beta features are available for registered users only, and the improvements are intended to serve our readers and unregistered users as well. Therefore, using beta features only would give us feedback from a very specific type of user that is not representative of our entire base of users. And moreover, we wish to receive the readers' and anonymous users' feedback from the earliest deployments.

What are the feature's success metrics?
Increase utility among our existing audiences, proxied by:


 * Interactions
 * Increase searches per session by 5% over the course of the project
 * Increase language switching per project by 5% over the course of the project


 * Affinity
 * Increase in positive and welcoming sentiments towards the site (via surveys and user testing)
 * Increase in sentiments of trust and credibility (measured via surveys and user testing)

As we define the changes we want to make with more specificity, we will expand and iterate on this list.

Why is the width of the content limited?  Why is there so much white space?
There are two reasons why we believe a layout with a max-width constraint will be beneficial to readers and editors:

Readability
The Wikipedia page on Line Length provides a good overview, as does the essay Size Matters: Balancing Line Length And Font Size In Responsive Web Design by Professor Laura Franz. The research study Computer text line lengths affect reading and learning by By Peter Orton, Ph.D. IBM Center for Advanced Learning is a more rigorous, academic study. The popular recommendation is that there should be between 40 and 75 characters per line. The findings of multiple studies conclude that "short line lengths are easier to read", and furthermore regarding learning and information retention "Subjects reading the narrow paragraphs had better retention than those reading the wide paragraphs".

In short, a maximum width allows for better readability, less eyes strain, and better retention of the information itself.

That said, we recognize that much of the content on our projects is meant to be scannable and we wanted to optimize for both scenarios and thus we landed a bit above the recommendation. We settled on an absolute width of 700pixes, which gives us between 59 and 109 characters per line.

Establishing a common reading experience
The second reason we think introducing a max-width could be beneficial to the reading experience is because it would work towards establishing a common experience for readers and editors. This should allow editors when making decisions about page layouts. The width the editor sees is the one the reader will see eventually. Currently an editor might be editing a page at a width of 1500px, while a reader reads it at a width of 1200px. By implementing a max-width we don’t remove this discrepancy completely (because there would still be variation below the fixed-width, for people with narrower screens), however we would be greatly limiting the range of variation.

For more details on our rationale and the process through which we selected the exact width, please go to the limiting content width project page.