For curious, I wanted to share a quick update on the typography refresh.
The following four recent pieces of news that should be of interest...
1). The French Wikipedia community closed their vote on most aspects of the
new design (color, size, new headers, etc.) and it was very much in favor
of keeping the new design in all aspects.[a]
2). Spanish Wikipedians also closed their vote, which was more of a simple
yes/no on whether to revert. This was also in favor of keeping the new
3). Jon Robson has put up a patch to allow LESS styles to be set
per-language.[c] This means that many local site hacks, like Japanese
Wikipedia removing the serif headers or Farsi Wikipedia having to set
completely different Farsi-friendly fonts, will potentially no longer be
necessary. Review and testing is needed!
4). For some time now MediaWiki.org and the test replica of English
Wikipedia (en.wikipedia.beta.wmflabs.org) have been using a new proposed
body font stack by Erwin Dokter. This puts Nimbus Sans L first, and
restores the other body font settings like Helvetica Neue for Mac users,
Arial for all Windows users etc. Please try it out, especially if you're on
Windows or Linux. We'd like to put this in Vector/core at some point, if we
can make sure it works.
On Apr 29, 2014 3:43 AM, "Steven Walling" <swalling(a)wikimedia.org> wrote:
> FYI, if you're interested in continuing to talk about this and related
> issues, I strongly encourage Wikitech subscribers to join the Design list.
> ---------- Forwarded message ----------
> From: Steven Walling <swalling(a)wikimedia.org>
> Date: Mon, Apr 28, 2014 at 6:42 PM
> Subject: Typography refresh, now that dust has settled
> To: "A list for the design team." <design(a)lists.wikimedia.org>
> Hi everyone,
> For curious, I wanted to share a quick update on the typography refresh.
> The following four recent pieces of news that should be of interest...
> 1). The French Wikipedia community closed their vote on most aspects of
> new design (color, size, new headers, etc.) and it was very much in favor
> of keeping the new design in all aspects.[a]
> 2). Spanish Wikipedians also closed their vote, which was more of a
> yes/no on whether to revert. This was also in favor of keeping the new
> 3). Jon Robson has put up a patch to allow LESS styles to be set
> per-language.[c] This means that many local site hacks, like Japanese
> Wikipedia removing the serif headers or Farsi Wikipedia having to set
> completely different Farsi-friendly fonts, will potentially no longer be
> necessary. Review and testing is needed!
> 4). For some time now MediaWiki.org and the test replica of English
> Wikipedia (en.wikipedia.beta.wmflabs.org) have been using a new proposed
> body font stack by Erwin Dokter. This puts Nimbus Sans L first, and
> restores the other body font settings like Helvetica Neue for Mac users,
> Arial for all Windows users etc. Please try it out, especially if you're
> Windows or Linux. We'd like to put this in Vector/core at some point, if
> can make sure it works.
> c. https://gerrit.wikimedia.org/r/#/c/125760/
> Steven Walling,
> Product Manager
Is there at this time any interest for a test tool for fonts where users
can rate the qualities if a font we are looking for? I posed the same
question on wikitech before the dust settled, but that might have been too
> Steven Walling,
> Product Manager
> Wikitech-l mailing list
I have uploaded a new version of the Winter prototype, version 0.5.
You may play with it here: http://unicorn.wmflabs.org/winter/
And give feedback here: https://www.mediawiki.org/wiki/Talk:Winter
After a significant battery of tests, several changes have been made (and will be going into test this coming week).
* Personal tools section no longer modifies itself upon scroll and remains fully expanded.
* In-header table of contents now appears to the left of the search box. It has been further expanded to include page-context links. The visual design of the menu requires work.
* Moved Language links into the page context ribbon area.
- Hovering over the affordance will show some languages to better enable discovery
- Clicking will open the language list. This could be the ULS; could be something else. But a pulldown list isn't working.
-This is for testing discoverability.
* Moved the watchlist star out of the context ribbon and right next to the article title.
* Some context-ribbon button labels are now automatically updating
- Discussions counts the sections in the talk page and changes accordingling (e.g., "35 Discussions") (We're aware that there are possible caching issues with live implementation)
- The history link now shows the last updated time in human-readable format.
A new experimental thing:
* Added new toggle, "Hidden Sidebar". This hides all sidebar links until hover over the logo.
- Toggle off or on from the sidebar.
- It needs a ''lot'' of work, especially around the "non-scrolled" visual state. This is possibly a throw-away experiment.
There are various other minor changes; full changelist can be found here: https://www.mediawiki.org/wiki/Winter#Version_0.5.2C_April_20.2C_2014
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Since no one answered, let me ask a different question – would anyone oppose if I were to remove the .mw-ui-quiet class?
On Thu, Mar 27, 2014 at 4:04 PM, Bartosz Dziewoński <matma.rex(a)gmail.com>wrote:
> Actually, what is the rationale for having a separate "quiet" style?
> The one that seems to be given here seems to be the "inverse Fitts' law"
> , but I don't really see how just making a button more bland helps with
> I'd be all for killing it and sticking to a simpler visual convention,
> just using regular (non-colored) buttons where we'd previously try to use
> the quiet ones.
>  http://blog.codinghorror.com/the-opposite-of-fitts-law/
(Resending because something ate the previous one.)
All the components you mentioned other than the switch to LESS and the animations used by hovercards for instance were actually created over a year ago before the start of the mediawiki.ui work. I can talk further with the developers about the performance issue, but yes, it's only part of the issue. As I said before I don't think it fits stylistically with the direction of the mediawiki.ui
Sent while mobile
On Apr 5, 2014, at 3:51 AM, Erwin Dokter <erwin(a)darcoury.nl> wrote:
> On 05-04-2014 05:57, Jared Zimmerman wrote:
> Nemo, when I say we, I mean the people responsible for the look and
> implementation of mediawiki.ui I've also been informed by the developers
> that drop shadows like the one proposed have a serious performance
> impact, especially on older browsers. The proposed style shown in the
> typography refresh is much simpler from a code perspective as well.
I find that slightly contradictory, when every new UX feature/extension has made heavy use of the newest CSS trickery, including transparency, animations, fade-ins, rounded corners and drop shadows. Everything that pops up on Wikipedia has them: Echo notification, watchlist notifications, ULS popups and everything else I can't think of.
With that in mind, the performance argument is a misnomer; older [define?] browsers tend not to support shadows anyway, so no problem there. The code is also *not* more complicated when done in LESS.
You just don't like the style, that is fine. It was intended to be a local CSS framework for templates anyway.
Since the typography update got pushed we are now left with
* Changes to the table of contents
* Changes to thumbnails
* A cleanup of external links.
What should we do with these remaining changes?
We could either
1) Package them into a single new beta feature
2) Package each of them into individual beta features e.g. Vector
table of contents tweaks, Vector thumbnail tweaks, Vector external
3) Submit each of these as patches to Gerrit (unless there are any complaints)
4) Throw them away