Something that came up yesterday when I was discussing with User:Rexx about the new WikiFont, is how it will influence accessibility, since it is actually a 'character' that will have effects on screenreader software. I have no idea what the effect will be, so if we start using that, I very much encourage that we should go and find out and then document some of the knowledge we gather into it's style and usage recommendations guidelines.
DJ
On bug 65317 [1] it is suggested that the preferences page should have
buttons aligned to the right and should be ordered so constructive is
the last. I've written a fix for this and I would appreciate some code
review.
This had me wondering, should this apply to all forms? e.g. the editing form
If so I think we probably need to get this into the style guide in
some form, detailing how buttons should be ordered. We may want to
introduce mw-ui-button-group or mw-ui-form-button-group.
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=65317
On 09/04/2014 03:29 AM, Monte Hurd wrote:
> The font forge importation workflow was sticky enough (importing svgs
> and mapping them, etc) that small visual tweaks (baseline offsets and
> such) ended up being made in the font forge project itself as well,
> thus diverging from the source svgs.
This is why automation and having a clear understanding of what the
source code is are both so important.
> I think this workflow stickiness was what led the designer to see the
> font forge project as canonical.
Actually, it was somewhat ambiguous what the source code is. Read
https://gerrit.wikimedia.org/r/#/c/137888/ if you want to know what I mean.
> One automates creating a font from a folder of svgs. Svgs are
> canonical as they should be, but hey, you want a font? You got it.
Great. This will be useful for the app, and if we ever decide to
revisit the decision about icons on web (I completely agree SVG is
better as source code, but we could still use generated fonts on desktop
if we decided that approach was suitable).
Matt Flaschen
On Friday, September 5, 2014, <design-request(a)lists.wikimedia.org> wrote:
> Send Design mailing list submissions to
> design(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/design
> or, via email, send a message with subject or body 'help' to
> design-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> design-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Design digest..."
>
>
> Today's Topics:
>
> 1. Re: Getting $wgUseMediaWikiUIEverywhere = true to be the
> default (Tomasz Finc)
> 2. Re: Style guides at Lonely Planet (Tomasz Finc)
> 3. Re: Getting $wgUseMediaWikiUIEverywhere = true to be the
> default (Erik Moeller)
> 4. Re: Getting $wgUseMediaWikiUIEverywhere = true to be the
> default (Steven Walling)
> 5. Re: Getting $wgUseMediaWikiUIEverywhere = true to be the
> default (Jared Zimmerman)
> 6. Re: Style guides at Lonely Planet (Jared Zimmerman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 5 Sep 2014 13:55:23 -0700
> From: Tomasz Finc <tfinc(a)wikimedia.org>
> To: "A list for the design team." <design(a)lists.wikimedia.org>
> Cc: Rachel diCerbo <rdicerbo(a)wikimedia.org>
> Subject: Re: [Design] Getting $wgUseMediaWikiUIEverywhere = true to be
> the default
> Message-ID:
> <
CAMxhqbcX4gVFfthN0vnxrTm0VicB5UrFG4yuO_GxjVuDhLwj3w(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Thu, Sep 4, 2014 at 4:24 AM, Jon Robson <jrobson(a)wikimedia.org> wrote:
>> 1) Enable MediaWiki UI everywhere
>>
>> Developers: Add $wgUseMediaWikiUIEverywhere=true into your LocalSettings
>> Non-developers: Explore http://mwui.wmflabs.org/wiki/Main_Page or
>> http://en.m.wikipedia.beta.wmflabs.org/ (the mobile site already
>> enables these to be the default)
>>
>> 2) Navigate around the site and make a note of interfaces that look
wrong.
>> Please file bugs against them here [1]
>> * Places where buttons are constructive when they should be
>> destructive / progress
>> * Take screenshots of interfaces that look cluttered/cramped.
>> * Identify pages which do not use MediaWiki UI styles at all
>>
>> 3) Let's fix the bugs
>>
>> 4) When this is all done, we will need to engage the
>> community/communicate this change. We might need to run a beta
>> feature. I'm hoping Jared or Steven can oversee this. Alternatively we
>> might just want to turn it on if we do not consider it a massive
>> change.
>
> Is there a good forum for us to engage and recommend how community
> members can get involved with at Step #1 ? That feels like it would
> give us the sense of scale and community participation from the
> beginning.
>
> CC'ing Rachel to see what she thinks
>
> --tomasz
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 5 Sep 2014 14:02:43 -0700
> From: Tomasz Finc <tfinc(a)wikimedia.org>
> To: "A list for the design team." <design(a)lists.wikimedia.org>
> Subject: Re: [Design] Style guides at Lonely Planet
> Message-ID:
> <CAMxhqbfHe2Sn=
k2vdW04VrH26XZFYyz++5azBCmH4BLLyZHuWA(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Very interesting read and I've been watching a good chunk of the videos
from
>
> https://www.youtube.com/channel/UCFdA1LIvjYDLrqeHiZphNWA
>
> Jared, where is our style guide at this point? I last checked in on it
> around Wikimania.
>
> Also, have you had a chance to watch
>
> Ian Feather: Reducing Complexity With a Component API ?
>
> --tomasz
>
> On Tue, Jul 29, 2014 at 3:15 PM, Jon Robson <jrobson(a)wikimedia.org> wrote:
>> Relevant to our interests...
>>
http://engineering.lonelyplanet.com/2014/05/18/a-maintainable-styleguide.ht…
>>
>> _______________________________________________
>> Design mailing list
>> Design(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/design
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 5 Sep 2014 14:08:22 -0700
> From: Erik Moeller <erik(a)wikimedia.org>
> To: "A list for the design team." <design(a)lists.wikimedia.org>
> Subject: Re: [Design] Getting $wgUseMediaWikiUIEverywhere = true to be
> the default
> Message-ID:
> <
CAEg6ZHkb75ORP0DUKL10e-PvZy8PwciWAuyAvEEHZJ-bfQkA1g(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks, Jon, for continuing to keep the pressure on.
>
> The appearance/size change for e.g. checkboxes is very noticeable, and
> right now it's inconsistent with other controls that are nearby, like
> radiobuttons and dropdowns. The first thing is to actually finish the
style
> guide and consistently apply it.
> http://tools.wmflabs.org/styleguide/desktop/index.html is very incomplete
> right now, when can we expect an updated version, or is there another one
I
> should be looking at?
>
> Thanks,
> Erik
>
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
"Wikipedia already looks great ... just add .m (on desktop)"
https://news.layervault.com/stories/31897-wikipedia-already-looks-great--ju…
For those unfamiliar, this is a designer's equivalent to Hacker News.
Interesting to see professional UX designers be less forgiving towards the
WikiWand design, in addition to the warm fuzzies from the love for the
mobile site.
This kind of feedback makes me wish you could set your desktop skin to use
mobile (aka Minerva). Or may e have clicking the "mobile view" link set a
cookie for my session to auto-redirect to mobile. Otherwise, it's hard to
evaluate how the mobile view stands up over sustained use on desktop.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/