I just love this Google I/O 2013 talk on human perception and
cognition, and its implications for interactive and visual design. It
is accessible, but with a lot of information and applies very well to
us I think.
I'm sure that many designers know all about this and some have
probably seen the clip before, but it is also very good for
developers, because many of these things we know subconsciously, but
it's not really part of our vocabulary.
https://www.youtube.com/watch?v=z2exxj4COhU
DJ
Hi all,
This is a heads up about some of the things the Growth team is thinking
about and working on with mediawiki.ui.
1. We're in the process of adding optional icon support for mediawiki.ui
buttons, with browser support down to IE8.[A]
2. We're going to get rid of the text shadow on the default mediawiki.ui
buttons.[B] It's distracting and doesn't increase readability. We don't use
gradients in the colored buttons for similar reasons.
3. We need to do some tweaking of the design of the default mediawiki.ui
button.[D] We're designing the second iteration of the anonymous editor
signup invitation UI to A/B test.[E] When looking at these, you can see
that the default mediawiki.ui button ("continue editing") almost seems
disabled. We should talk about ways to improve on this design, such as
darkening the text color or giving the default button a background color.
This may come up in the WMF UX team's weekly design review as well, but I
wanted to give a heads up about these issues since the library is in
MediaWiki core.
A. https://bugzilla.wikimedia.org/show_bug.cgi?id=55535
B. https://bugzilla.wikimedia.org/show_bug.cgi?id=61940
C. These are viewable at
https://en.wikipedia.org/wiki/Crocodilia?gettingStartedReturn=true if
you're logged in
D. See style guide:
http://tools.wmflabs.org/styleguide/desktop/section-2.html
E.
https://www.mediawiki.org/wiki/Anonymous_editor_acquisition/Signup_invites_…
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
Hi,
I wondered where to raise this and decided to do it here.
The message that asks for to write the edit summary in VisualEditor is
"Describe what you changed".
In the source editor it's just "Summary" in the core. In the English
Wikipedia, however, it's modified to "[[Help:Edit summary|Edit summary]]
(Briefly describe the changes you have made)".
The VisualEditor is used a lot by new editors (it's an impression, but I'm
pretty sure that the data will say the same). The idea of the edit summary
is to help the people who patrol recent changes or read the article
history. When new editors, who aren't so familiar with Wikipedia's edit
summary culture, are asked to "Describe what you changed", they may answer:
"the year when he was born". This is a correct answer as far as the editor
is concerned, but it's not so helpful in the context of recent changes.
I don't know about other languages, but this actually happens quite a lot
in the Hebrew Wikipedia, and some patrollers are complaining about it. (In
grammatical terms, the summary is written as a direct object: "Describe
what you changed" -> (I changed) "the year".)
Now I could change this to something clearer in the translation to this
particular language, but I like to be thorough when it comes to UI
messages, so I'd like to ask the pros here: How would you design the edit
summary box? The requirements I can think of are:
1. Encourage the user to actually write the edit summary. People not
writing summaries at all is a bigger problem than writing them not clearly
as I wrote above.
2. Encourage to write it in a way that would be useful to the people who
will read them in Recent Changes and in reviewing previous article versions.
3. Possibly give the users tips about how to write them well, but without
too much additional text.
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore