Ryan is suggesting we use the free font Linux Libertine instead of
Georgia/DejaVu as our free font offering on the basis that we use this font
in the Wikipedia logo.
This sounds good.
What think you designers?
I wrote some jQuery to generate all the 'mw-ui-button mw-ui-big
mw-ui-constructive' button variations.
On https://www.mediawiki.org/ and http://ee-flow.wmflabs.org/ ,
if you edit your User:<myname>/common.js and add to it
importScript( 'User:Spage/agoraPanel.js' );
then save and shift-Reload, then in the left-hand navigation area you
should see a button that inserts a whole mess of Agora buttons, and also
some checkboxes to load button CSS modules.
Let me know if you have problems and feel free to improve it. This isn't
to take away from the living style guide (now in core!), which will guide
people in using buttons well, it's just a tool to see them all when
developing LESS/CSS.
--
=S Page Features engineer
Hey,
[This question is in particular directed at Jared, Jon, May, and Vibha as
the authors of the current Typography Refresh in Vector, but I wanted to
post to a public list just in case.]
As you can see at mediawiki.org/wiki/Talk:Typography_Update there is a ton
of feedback to wade through. I think it was wise to have it out as a Beta
feature for a while before making any changes, but we've got more than
enough commentary to get a sense of things.
I vote we set up time to do a pass through the feedback and refactor as
necessary, after the holidays. So sometime in January.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
(Congratulations on the Flow alpha release showing off your fine UX work!)
Some users somewhere said that the Full view - Collapsed view - Small view
trio of icons on Flow boards don't act like buttons. They're currently
"dead" apart from the cursor change.
They seem to me like quiet action buttons such as Cancel, that don't have
the border and beveled bottom of CTA buttons. So like Cancel they should
have a mouseover state.
But I notice that quiet Cancel in Flow has no mouseover state, while it
does have an undocumented click state which lightens to something that
looks like a disabled state... but Cancel has no disabled state.
Also I recall May and Juliusz at the UX hack #3 deciding to flip the normal
and mouseover state so you can see the
neutral/progressive/destructive/constructive colors of quiet buttons by
default, even on a tablet. But Agora Control Library says the opposite,
"Button with Neutral null state and Progressive/Destructive/Constructive
hover, click, or post-click state"
We need a more definitive Agora button spec with all four states (normal,
mouseover, click, disabled) for both quiet action buttons and CTA buttons,
for all four types (neutral/progressive/destructive/constructive). 32
flavors! Or 40 if "post-click state" is an additional state.
Jared, May, Juliusz: I uploaded the annotated diagram I made from
Agora_specs.pdf's "Buttons" page, it's in <
https://www.mediawiki.org/wiki/Wikimedia_Foundation_Design/Agora_Control_Li…
>
Yours mw-ui-constructive-ly,
--
=S Page Features engineer
If you are in beta on mobile now, there's a new look for the editor. The
heading of the editor now says "Editing [article name]" in English.
The problem is that designers want this to be always one line long at
most and truncate it when it's longer. This is fine in English where
"Editing" is at the beginning, not OK in some languages, e.g. Japanese:
http://tinyurl.com/qftpgy4 (click the pencil icon)
where "editing" ("編集中") is at the end. If we truncate this, it won't
make much sense.
Should I suggest in the message description that the translators should
use such a grammatical construction so that the word "editing" stays at
the beginning? That's what designers suggested.
--
Juliusz
Hi.
I've begun attempting to articulate what design means in Wikimedia's
context at <https://meta.wikimedia.org/wiki/Design>. I hope some of you
will join me. :-)
MZMcBride
Greetings!
Can you help us create a better multimedia experience on Wikipedia and its sister sites?
If you are interested, we'd like to invite you to join a special Multimedia Meetup at the Wikimedia Foundation, this Monday, December 9 at 6:30pm PST.
This one-hour event will bring together dozens of developers and community members to discuss how we can use images, sounds and videos to help people learn more effectively on our sites.
To join us, simply sign up here:
http://www.meetup.com/wikimedia-tech/events/123456892/
If you know anyone else outside WMF whom you think would be interested, you are welcome to spread the word in your community -- the more, the merrier :)
We will start our meeting by presenting a vision for multimedia in 2016 and ask you how we can improve it.
We will then demo and discuss these new projects together:
* media viewer
* file feedback
* new video formats
* campaign tools
As a group, we will brainstorm new ways to view, contribute, curate, discover and use media files on Wikipedia, and grow our audio-visual knowledge base in the process.
This is a great opportunity to plan our next steps together and network with other like-minded community members. And we'll be serving free drinks and pizza to make this even more fun for you. :)
Images, sounds and videos can engage users more deeply than text articles, and better support their individual learning styles. To that end, we aim to help more users to collaborate through multimedia -- by improving their viewing experience, supporting their media contributions, and making it easier to use media in articles.
We look forward to your advice on how to make this vision happen together.
Thanks for your consideration. We hope to speak with you soon. :)
All the best,
Fabrice
_______________________________
Fabrice Florin
Product Manager, Multimedia
Wikimedia Foundation
http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF)https://www.mediawiki.org/wiki/Multimedia