Suggestion: Add this CSS to [[MediaWiki:Common.css]]

Looks reasonable. Maybe our ui designers could give a quick look and comment this.

Nike (talk)16:06, 23 January 2012

Do we have any UI designers, then? :)

Siebrand10:08, 24 January 2012

That was my question too :P

Anyways, the "problem" here is two-fold: in one hand, it is important to show that there is no documentation message, so that you can invite the user to post a documentation of it if he/she knows it; on the other hand it is nice to show that there actually is a documentation message vs. there is none (which currently isn't very clear because of the aforementioned reason). The best solution in my mind is to separate the two visually, and the way I did it on Meta is one of the simplest: show an icon of there is documentation, don't show one if there isn't. I think this has an advantage over, e.g., colour coding, since it makes it obvious when there is an information message.

Jsoby (talk)01:53, 25 January 2012

How does having an icon have advantage over color? The way I see it, if the entire message "There is no documentation..." was on a red background, that'd be much more noticeable than an icon.

 

That was half-joke. We've been promised some UI resources, but we have hard time using any. On the other hand I'd really like some designer to chip in how we should approach the problem.

Nike (talk)08:18, 25 January 2012

We'll probably have an opportunity in Pune. If you remind me while I'm there, I'll get you in a Skype session...

Siebrand23:57, 26 January 2012
Edited by another user.
Last edit: 21:17, 4 December 2012

We should have some resource now. It's probably taken care of in the current designs, but I'm not certain.

Nike (talk)08:51, 6 March 2012

Niklas, can you ping Pau and Arun about this?

Siebrand21:16, 4 December 2012
 

Showing the "No documentation" warning in the same way that documentation itself as it happens now is problematic for the UI. To distinguish them for the new designs we are removing instead of adding:

For "no documentation" we proposed to remove the message and provide a direct call to action ("Add description/documentation") and where it is just provide it without the need to label it as documentation.

Some examples:

By reducing the number of labels, boxes and marks we are trying to provide a UI that is clean and quick to process by the user. If we later find that more emphasis is needed, we can add an icon for the documentation and/or show the "no documentation" message grayed-out.

Pginer (talk)16:14, 20 December 2012