- right cognitive load = marketing speak for dumbing down
- user experience similar across platforms = marketing speak for a compromise that doesn't make optimal use of the capabilities of each platform.
Talk:Contributors/Projects/Accessible editing buttons
Wikipedia has been taken over by marketing
@Zanaq Hi, I'm sorry that you feel we've been taking on marketing speech. Take notice, that the Wikimedia Foundation is behind this specific change and Wikipedia is only one of the projects we care about on several levels, among those, technologically. You might be aware of this already, wanted to point this out for others coming across this discussion though.
I would like to give insights as one of the people responsible behind these changes. We've been including several measurements in our user-interface library OOUI and in MediaWiki (the software building the fundament for Wikipedia and others) transforming pages to make use of this library – and our standard buttons and form elements.
You're pointing at “right coginitive load” and this is a bit of a blurry term. It originates from psychology and applies to user-interfaces and is a well-established and research backed umbrella term in user-experience circles. We actually try to reduce the cognitive load for users, for example by strengthening consistency (using the same buttons aka button appearances for the same actions across our interface) or grouping elements that belong together visually together. Please see this article for a rough collection of such measurements.
To your point about similar user experience across platforms: We designed OOUI to work on mobile and desktop in a user-friendly and accessible way. It's superior to the status quo (on non-OOUI using special pages) which fails on desktop on various occurrences. With an already big and steadily increasing amount of users accessing our products on mobile devices this is a pain point for many of our users. We try to improve their usage without sensibly adapting it on desktop as well. And I can assure you, that we're not stopping there, but go for specific improvements on platforms beyond this general, standardized fundament. We need this approach in order to be resourceful with our time and the donations. Not doing so and and working only platform-specific would not only make it harder for users to accomplish their tasks between different devices they are using or unable to use our website at all in a productive way, it would also be wasteful from a design and development perspective.
Hope I could give a bit of explanation for those expert terms used, which we didn't mean to use in a “marketing speak” manner. Please feel invited to participate by filing tasks tagged with #ui-standardization on our issue tracker Phabricator in order to make this a more satisfying approach.
Page navigation buttons
help page updated
The following buttons appear for navigating and editing the Page: namespace
- previous page
- next page
- the Index for the page
- But I am not able to view them in sa,wikisource.org. eg. page https://sa.wikisource.org/w/index.php?title=%E0%A4%AA%E0%A5%83%E0%A4%B7%E0%A5%8D%E0%A4%A0%E0%A4%AE%E0%A5%8D:A_Sanskrit_primer_(1901).djvu/%E0%A5%A7%E0%A5%A6%E0%A5%A8&action=edit
I am having no issue seeing the components, what I see ... phabricator:F10167247
This is in monobook skin, using standard editor, maybe difference may be how I am configured. [dinosaur settings]
[Also to note that as a global admin there are extra things that you normal users wouldn't expect to see.]
@Whatamidoing (WMF) it appears to have the same general configuration in that it uses proofreadpage extension. I doubt that it has the same local configuration. I will answer above question in situ.
Thank you both for your replies. I had been looking for the blue icons as shown in the en.wikisource help page. I have now found that there are black < > arrows for page navigation and ^ for Index. Thanks. ~~~~
Some changes are skin related, others are local customisation. One forgets when one uses a certain skin, and just editing at one site. I have modified the enWS text to indicate text and icons. Thanks for the note.
I think your changes has caused a problem for fa.wikisource. Before your changes, the proofread plugin was working well. But now I can use it only when I enter as an ip and not as registered user.
Hi. If it works properly as an IP editor, then the issue is almost certainly caused by a gadget. You should:
- Confirm that it is a gadget, using the details at Special:MyLanguage/Help:Locating broken scripts
- Determine which gadget it is
- Ask the gadget's maintainer to make the necessary updates (using the instructions on this page, i.e. Contributors/Projects/Accessible editing buttons#Fixing scripts)
Hope that helps.
I solved the problem simply by restoring all of the default settings.