"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
This is really a UX question, not design per se.
https://gerrit.wikimedia.org/r/#/c/104926/ (an under-review change) adds
a warning if you choose a username that needs to be
reformatted/canonicalized. For example, "my username" is changed to "My
It displays the warning, puts the new username ("My username") in the
box, then you have to retype your password (twice), then press enter to
The main potential benefit, as I see it, is that if you don't like "My
username" (the reformatted version), you can choose a different username
User experience feedback would be welcome; you can post on the change or
I'm very happy to announce the addition of Preteek Saxena as UX Prototyping
contractor to the UX Design team. Prateek will help the design team build
high fidelity mockups that allow us to do moderated and unmoderated user
testing with systems that test concepts outside the roadmaps of other
groups for early validation. Prateek will also aid in transitioning Explore
(20%) time experiments into code launchable as Beta Features.
Prateek is a developer with an eye for design. He has worked with
foundation developers on various projects in the past including the mobile
team. He has developed primarily for the web using frameworks like Ruby on
Rails in the back end and d3.js and jQuery on the front end. He has also
worked on design for the web, mobile and print.
When Prateek isn't making beautiful functional prototypes he can be found
working on game prototypes http://xvii.in/ & http://vertigo.clay.io/ and
making music with friends https://soundcloud.com/bowl-of-petunias
Prateek will be working with my team and product managers to bring static
design concepts to life. He will initially be focused on Navigation Popups
and Fixed Header Beta Features, but will certainly branch out to work with
us on other projects. He is located in Mumbai, so you'll mostly see him on
IRC or via email.
*Jared Zimmerman * \\ Director of User Experience \\ Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmerman<https://twitter.com/JaredZimmerman>
Welcome Prateek! Good to have you on Jared's awesome UX team!
Director of Engineering
Internationalization / Localization
On Fri, Jan 31, 2014 at 11:36 AM, Heather McAndrew
> Welcome Prateek!!
> *Heather McAndrew*
> *415-839-6885 <http://www.linkedin.com/in/recruitervolunteerheather/> ext.
> Follow us on Twitter @wikimediaatwork
> We welcome you to contribute to Wikipedia: http://bit.ly/Imnhhttp
> Developers-Join us on IRC: http://bit.ly/VC07xq
> Become a Product Advisor: http://bit.ly/R1obwD
> On Fri, Jan 31, 2014 at 10:48 AM, Jared Zimmerman <
> jared.zimmerman(a)wikimedia.org> wrote:
>> Hello All,
>> I’m very happy to announce the addition of Preteek Saxena as UX
>> Prototyping contractor to the UX Design team. Prateek will help the design
>> team build high fidelity mockups that allow us to do moderated and
>> unmoderated user testing with systems that test concepts outside the
>> roadmaps of other groups for early validation. Prateek will also aid in
>> transitioning Explore (20%) time experiments into code launchable as Beta
>> Prateek is a developer with an eye for design. He has worked with
>> foundation developers on various projects in the past including the mobile
>> team. He has developed primarily for the web using frameworks like Ruby
>> on Rails in the back end and d3.js and jQuery on the front end. He has also
>> worked on design for the web, mobile and print.
>> When Prateek isn’t making beautiful functional prototypes he can be found
>> working on game prototypes http://xvii.in/ & http://vertigo.clay.io/ and
>> making music with friends https://soundcloud.com/bowl-of-petunias
>> Prateek will be working with my team and product managers to bring
>> static design concepts to life. He will initially be focused on Navigation
>> Popups and Fixed Header Beta Features, but will certainly branch out to
>> work with us on other projects. He is located in Mumbai, so you’ll mostly
>> see him on IRC or via email.
>> some links:
>> *Jared Zimmerman * \\ Director of User Experience \\ Wikimedia
>> M : +1 415 609 4043 | : @JaredZimmerman<https://twitter.com/JaredZimmerman>
>> Wmfall mailing list
> Wmfall mailing list
FYI. For designers on the list, this is also on Beta Labs right now, though
some patches are still needing merge before Thursday.
---------- Forwarded message ----------
From: Steven Walling <swalling(a)wikimedia.org>
Date: Wed, Jan 29, 2014 at 9:09 PM
Subject: Small update to button styles in MediaWiki core
To: Coordination of technology deployments across languages/projects <
This is just a notice that we are making a small series of updates to the
button styles in MediaWiki core. These buttons appear on login, account
creation, search, and some other interfaces.
This isn't a big change, but I didn't want anyone to be taken by surprise
since there are some color changes and so on. On the positive side, those
who think our blue action buttons are too Facebook-like may be pleased with
the change. ;-)
This is added to Tech News next issue, and you will be able to see it on
mediawiki.org as of Thursday, if you want to try it out before it is on
I’ve been making a thing. It’s actually got a code-name now! No more saying “Vector static header and navigation modification”.
LOTS of stuff going on with this update. Notably:
* Now asks for a username on load, so as to set things up
* All pages are loaded from the API via JSON. So it’s not just the single static page.
* Got rid of pretty much every color.
* Article actions now dock in the header as you scroll.
* Table of Contents is now in the header from the beginning
* The sidebar’s border goes away as you scroll past it
* Lots of links/actions do what you think they should. Most do not.
You can play with it here: http://unicorn.wmflabs.org/winter/
And read more about it here: https://www.mediawiki.org/wiki/Winter
Here’s your changelog:
== Changes, January 20 ==
* New code name: Winter
* System now prompts for a user name upon load and will optionally save the value.
** This sets up the personal bar to be, well, personal.
** This action ''DOES NOT'' log the user into Wikipedia.
** Saved data can be cleared from the sidebar.
* Searchbox now drops text on focus and replaces it on blur
* Searchbox now has a hover state with invitation text.
* Searchbox icon now turns blue on focus
* Logo now snaps to white background when in locked position.
* Sidebar is now white by default, with a grey border that fades out when all items in the sidebar are out of view.
* The Table of Contents now appears in the header of the page from the beginning
** (Previous versions of Winter had the ToC only appear there after the in-page Table of Contents rolled off-screen)
* Article actions now dock in the header when they scroll out of view (iconfied).
* Added tipsy behaviors.
* Fixed issue with search box positioning.
* Added pencil icons to section edit buttons
* Section edit buttons now are visible at all times but do not have borders.
** On hover, they turn blue.
* Changed section edit hover transition from 'linear' to 'ease'
* Added footer section
* Added "categories" box in example article
* Added "Typography" toggle in sidebar. Activating it turns on:
** An approximation of restricted measure
* References have returned
* Built a JSON parser into the demo so that different pages can be loaded via the API.
* Language links are now slotted into the sidebar.
* System correctly recognizes when it's looking at ''User'' content (User: and User_talk:) and adds icons and functionality as required
* Handles contributions (sort of - buggy)
=== Known Issues ===
* Contributions views:
** Timestamps don't sort right
** Comment fields are not correctly parsed from wikitext to html
** Size changes are not correctly reflected
* Redlinks do not work
* System does not handle 404 loads correctly (fails silently, requires reload)
* Internal hash URLs don't scroll correctly
* Some buttons don't go away when they should
* Loading from JSON breaks the nice little "section hover" stuff.
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Today I worked on finishing the new buttons styles. They're mostly done
but I would like to clarify a few things. You can preview the current
version by downloading https://www.dropbox.com/s/b1sn1x4slkwgqs9/buttons.zip
Every button variant has 4 subvariants:
* quiet disabled
1. The colors. I took them from
https://www.mediawiki.org/wiki/File:Guide_Color.png but blue looks kind
of dim. Blue, green an red also don't seem to have the same level of
perceived lightness. Is that OK?
2. Quiet buttons. I remember clearly from talking to May that we wanted
them to be colored in their default state and make them slightly darker
in hover. I don't remember what they were supposed to look like when
disabled. Right now they're slightly lighter but maybe they should be
3. Focus state. Right now it's the same as hover state, but I'm afraid
it might not be enough for people with poor vision or color-blind who
use keyboard for navigation. Opinions?
I just noticed that the line-heights we're using for content text are
significantly different between the mobile typography refresh and the
desktop typography refresh (VectorBeta).
On mobile, we're now using 1.65 (this is a multiplier against font-size),
while on desktop we're still using 1.5. Do we want to increase desktop to
1.65 as well (or use 1.6 as a compromise for both)? Any thoughts or
opinions? My opinion is that we should use the same value for both and that
it should probably be increased on desktop.
Hi, thanks for letting us know about this project.
I read through the design document, and there's definitely a lot of good
ideas in there. I particularly agree with the list of questions the new
site is supposed to answer, especially with regards to new, perhaps
I just mocked up a little live demo of what I could imagine the new
homepage to look like with regards to the points discussed in the design
Please feel free to check it out over here:
I'd really like to contribute to this project, and any feedback on my
proposal is very appreciated. A summary of my specific design decisions
and why I made them will follow shortly.
best, max. @awesomephant <https://twitter.com/awesomephant>
April 2 to 5 in Leipzig, Germany
-------- Original Message --------
Subject: Spreading the word
Date: Thu, 16 Jan 2014 11:43:01 -0600
From: Nathan Willis <nwillis(a)glyphography.com>
Random thought -- I don't know why this hadn't occurred to me earlier --
but are there Wikimedia people who would be interested in coming to
Libre Graphics Meeting? Obviously you deal a lot more with the
publishing side of things, while (historically) LGM has been focused on
content-creation tools like Blender and GIMP.... But if there are
Wikipedians who would be in the area, they might find LGM helpful for
content-publishing stuff as well; in particular there are a lot of font
and typography talks in recent years, thanks to CSS @font-face. For
that matter, there is typically a lot of W3C and CC-licensing content in
the mix as well. It's not just the app-development teams that make the
event work; one of the best parts is getting the developers face-to-face
time with the people using their stuff on a daily basis.
Anyway, to the point: LGM this year is going to be April 2 to 5 in
Leipzig, Germany. The site is at http://libregraphicsmeeting.org/2014/
.... If there are interested people nearby, we'd love to have them join
us. Attendance is free; we try to underwrite travel costs for open
source developers who attend (which we would also love to see Wikimedia
take an interest in, of course :) -- tell your friends about the
"donate" link!). But really I'm more interested in making sure we
spread the word. If you use or build free creative-graphics software,
there's something for you at LGM.
Think there'd be interest? Or do you know someone in the organization
who might find it up their alley?