Reading/Web/Desktop Improvements/Frequently asked questions/sr

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 a max-width of 960px, which gives us between 90 and 150 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.

Када ће ове измене бити доступне на највећим пројектима?
Не 2020. године, осим ако се заједница добровољно не придружи нашем тестирању. Тренутно се усредсређујемо на развој наших првих функција на основу података које смо већ прикупили, као и на основу тестова на „пројектима раног усвајања”. Надамо се да ће измене постати глобално доступне 2021.

Да ли ће побољшања бити уведена на сродним вики пројектима и на викијима који нису писани латиницом?
Наравно. Већ смо направили списак „пројеката раног усвајања” на ком се налазе викији различитих величина и писма. Такође смо планирали да одаберемо бар један пројекат који није википедија.

На којим пројектима су ове измене доступне?
Ево списка пројеката на којима су побољшања доступна.


 * сродни пројекти:
 * 
 * 


 * пројекти који нису писани латиницом:
 * he:
 * fa:


 * википедије писане латиницом:
 * eu:
 * fr:


 * додатно:
 * Канцеларијски вики

Планирамо да проширимо ову листу.

Како да ово буде уведено на мој вики?
Ако сте заинтересовани да се побољшања уведу на ваш пројекат,
 * 1) постигните консензус са заједницом,
 * 2) обратите се коринсику SGrabarczuk (WMF) — имејл: sgrabarczuk-ctr@wikimedia.org — ако вам је потребна подршка.

Да ли ће се измене увести на Монобуку и Безвременској теми?
Не. Ове измене ће се применити само на векторску тему. [ Векторска тема] је подразумевана на Викимедијиним пројектима још од 2010. Побољшања нису доступна за остале тема, попут [ Монобука], [  Безвременске теме], [  Минерве] или [  Савремене теме].

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 SGrabarczuk (WMF), email: sgrabarczuk-ctr@wikimedia.org.

How can I disable it?
It's possible to turn the improvements on and off within user preferences. We have also provided an opt-out button in the left sidebar (accessible on each page):.

How can I report a bug?
You can add a task on Phabricator and add Desktop Improvements project tag or contact 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.