Just a note on fonts and licenses --
Google's been helping to make lots of high quality fonts available
under open licenses, and ships these with products like Chrome OS.
Their font directory repository is here:
https://code.google.com/p/googlefontdirectory/
And they have nice web UI for comparing fonts here:
https://www.google.com/webfonts
I don't think any of the uses we have right now outside i18n merit
using actual webfonts (for which the i18n team developed the WebFonts
extension), but it might be a nice nod to open source font development
to specify openly licensed fonts as preferred in cases where we're
currently pointing to proprietary fonts like the Microsoft core fonts.
Cheers,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Hi all,
I wanted to share a short video that illustrates some ideas for the user
experience improvement of the Translate extension.
The video is available at http://youtu.be/xKfaLyJE4ow?hd=1 (links to
different language-specific versions of the prototypes are available at the
video description)
Arun and I are organizing usability testing sessions these weeks. Anybody
can volunteer for participation in the usability tests at
http://goo.gl/E5dvO
The only requirement is to speak more than one language, but no previous
experience with translation is required.
Feel free to provide any comment on the prototype, or join the testing
sessions.
Pau
--
Pau Giner
Interaction Designer
Wikimedia Foundation
Hi,
I made a quick CSS experiment to make the map for the Universal Language
Selector less prominent (by hiding region labels) so that it does not
compete with the search bar for user attention.
It can be tested at http://goo.gl/XhWuC
With this approach:
- For users that use search (most of them), the map becomes less
distracting to find the search bar (the main entry point).
- For users browsing the list (the ones that need the map), a blue line
provides feedback about where in the map they are, and serves as an
invitation to interact. Labels appear when users hover the map.
On the other hand, de-emphasizing the map implies making it less clear that
it is an interactive element. We will be including a test for our next
round of tests to compare the current approach with this one to verify that
new problems are not introduced. Meanwhile, feedback is welcome.
For an insight on how the current selector is used, the video we make with
some of the users that tested the selector is available at
http://youtu.be/ZbUhuAvyPr4
Pau
--
Pau Giner
Interaction Designer
Wikimedia Foundation
FYI
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Fri, Oct 12, 2012 at 2:18 PM
Subject: Re: [Wikitech-l] Prefs removal
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
On Mon, Oct 8, 2012 at 11:12 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> I've pinged analytics to see if they can get us a better prefs report.
Dario Taraborelli has kindly made a detailed dataset of preferences
available. He can chime in with details if needed.
The dataset can be found here:
http://thedatahub.org/dataset/wikipedia-user-preferences
These datasets capture the following:
- user_properties set to '' from the default -> active_prefs_0
- user_properties set to 1 from the default -> active_prefs_1
-> NOTE: This can be very misleading for non-boolean prefs
- user_properties set to !='' from the default -> active_prefs_all
This is based on a dataset of _active_ users which is included.
Unchanged prefs aren't included, specific non-boolean settings aren't
included, and prefs with < 5 users aren't included. This is en.wp,
other languages to follow.
Note there's all kinds of funkiness with how prefs may be serialized
to the DB - prefs names and defaults may have changed, prefs may have
been removed, and some stuff is serialized when it doesn't need to be
(suggesting that prefs have been changed, when in fact the user has
just performed a pref save). But for a lot of the more obscure prefs
this should be good initial guidance.
Will post some initial observations to
https://www.mediawiki.org/wiki/Requests_for_comment/Core_user_preferences
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Forwarding in case anyone interested in design wants to opine on the
main page design for Wikidata.
-------- Original Message --------
Subject: [Wikidata-l] Main Page design (Wikidata-l Digest, Vol 11, Issue 9)
Date: Fri, 12 Oct 2012 11:46:48 +0200
From: Lydia Pintscher <lydia.pintscher(a)wikimedia.de>
Reply-To: wikidata-l(a)lists.wikimedia.org
To: Discussion list for the Wikidata project.
<wikidata-l(a)lists.wikimedia.org>
Heya folks,
It's time we figure out what the Main Page of Wikidata should look
like. It'd be great if you helped out with this. I've started a page
on Meta here: http://meta.wikimedia.org/wiki/Wikidata/Main_Page_draft
We'll copy the content of that page to Wikidata once it's live.
Go crazy and make it useful and pretty ;-)
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Wikidata
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur F?rderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinn?tzig anerkannt durch das
Finanzamt f?r K?rperschaften I Berlin, Steuernummer 27/681/51985.
I want to share a 7 min. video of users interacting with the initial
implementation of the language selector:
http://www.youtube.com/watch?v=ZbUhuAvyPr4
The video includes fragments from the users that agree to make it public
their participation in the latest round of tests.
This round was based on the implementation available at
http://translatewiki.net (and not interactive prototypes as in previous
rounds).
Since Google Hangout was used for the recordings, the video quality is very
low. Nevertheless, making this public may help to make visible to the
community
that users are in the center of our design process, and encourage their
participation in future usability testing sessions.
Pau
--
Pau Giner
Interaction Designer
Wikimedia Foundation
hi Team,
here is a small set of Patterns that we should try and setup, these affect
some upcoming designs:
*1. Guide Text + **Help Hook ** associated with an Input Field:*
Capture: What does it look like, Where does it go, What is the Type
Treatment, Demonstrate the pattern with at least two examples, Discuss
Exceptions.
*2. Dismissing Page Notices*
Capture: What does it look like, Where does it go, What is the Interaction,
Is there any feedback?
Please do not respond with answers, if you have the time go ahead and mock
up the pattern and post to agora.
Thanks
Vibha
