"With humanizing articles, we have two objectives:
-Creating awareness about the editors and their interests on Wikipedia.
-Promoting connections within the community using shared interests."
The post shares some ideas and mockups and notes, "While the details are
being refined, comments on the general direction towards contributions
or alternate ideas would be super appreciated."
(By the way, after this email, I'm unsubscribing from the design list as
I prep for my sabbatical - more info at
. If you need to talk about Wikimedia technical community stuff or
communication before January, please consult Quim Gil, qgil at wikimedia
dot org, or Guillaume Paumier, gpaumier at wikimedia dot org. Thanks!
Looking forward to coming back in January.)
Engineering Community Manager
The main reason I suggested using Linux Libertine as the 'preferred' header
font instead of DejuVu Serif is that DejaVu Serif doesn't at all resemble
Georgia (the proprietary font the designers wanted). It's almost a
slab-serif font, which is very different from the book/antique serifs of
fonts like Georgia and Times. The designers wanted a classic,
"encyclopedic" looking font for the headers. DejaVu Serif is a workhorse
font, not a presentation/display font. It's appeal lies in its support for
thousands of Unicode characters, definitely not in its design (which is
frankly pretty awful). On pretty much any Linux system, specifying DejaVu
Serif in the CSS is going to be redundant anyway, since most of the popular
Linux installs fall back to DejaVu Serif as the default 'serif' font
anyway. Thus any characters that can't get rendered in the preferred fonts
will get rendered in DejaVu anyway.
When choosing the order of fonts in a CSS stack, you always put the
prettiest ones first, and the most widely installed ones last. In the
current case, we're doing it backwards.
I'm also open to using 'Nimbus Roman No9 L', which is more widely installed
than Linux Libertine, but a lot nicer to look at than DejaVu Serif. It's
basically a Times Roman replacement. Another option would be Liberation
Serif, which is pretty ugly, but still nicer than DejaVu Serif.
My preferred font-stack for the headers would be:
font-family: "Linux Libertine", Georgia, "Nimbus Roman No9 L", serif;
Really though, the preferred font should be chosen by the designers, not by
a committee of developers, IMO.
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
=S Page Features engineer
[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.
(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 <
=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.