Hi design folks,
At some point during the Wikimania DevDays, Benoît and I teamed up to imagine & try a few quick tweaks to Wikimedia Commons interface.
What we achieved in the end is a big “Upload a file” (« Importer un fichier » in French) button on the French-language main page. [1] [2] Our rationale was that it is unreasonable to have people look for the tiny link in the left menu bar.
Any thoughts on this? Good, bad, ugly?
I will probably suggest on the Village Pump in the next few days to have it on the English-language Main Page too (though the discussion will probably drift in the necessity of redesigning completely said main page and ending up nowhere in the end, or that we need a Guided Tour for that, or etc. ;-þ)
[1] https://commons.wikimedia.org/wiki/Accueil [2] Diff < https://commons.wikimedia.org/w/index.php?title=Template%3AAccueil%2FEnt%C3%...
Cheers,
On Sun, Aug 18, 2013 at 7:11 AM, Jean-Frédéric jeanfrederic.wiki@gmail.comwrote:
What we achieved in the end is a big “Upload a file” (« Importer un fichier » in French) button on the French-language main page. [1] [2] Our rationale was that it is unreasonable to have people look for the tiny link in the left menu bar.
Any thoughts on this? Good, bad, ugly?
I think the Agora buttons look nicer than the jQuery UI classes, <span class="mw-ui-button mw-ui-primary mw-ui-big">Importer un fichier</span> But, commons doesn't load 'mediawiki.ui' by default, probably because it isn't using Echo yet. And Special:UploadWizard isn't using Agora.
-- =S Page software engineer on Editor Engagement Experiments
On Mon, Aug 19, 2013 at 12:23 PM, S Page spage@wikimedia.org wrote:
I think the Agora buttons look nicer than the jQuery UI classes, <span class="mw-ui-button mw-ui-primary mw-ui-big">Importer un fichier</span> But, commons doesn't load 'mediawiki.ui' by default, probably because it isn't using Echo yet. And Special:UploadWizard isn't using Agora.
Isn't there a patch awaiting review/revision to load mediawiki.ui by default, to solve this very problem?
Anyway, looks good to me Jean-Fred. I agree with S the newer styles of button (like what we're using on login/signup) would look more consistent and stand out more too. But I don't think there's anything obnoxious about the new button you guys put up. Other than reading/viewing the featured Main Page content, uploading is the main action we want people to have access to, after all.
On 08/19/2013 03:27 PM, Steven Walling wrote:
Isn't there a patch awaiting review/revision to load mediawiki.ui by default, to solve this very problem?
Yes, it is https://gerrit.wikimedia.org/r/#/c/70740/ .
Matt Flaschen
Is there, anywhere, a documentation about the CSS classes used by the EE and E3 projects? This style or the other one: what does the guideline say?
This hack, as all new stuff created by the French crew, is made by extrapolation. We try to make it according to Agora specifications, but honestly, there is a small lack of documentation. :-)
Benoît Le 19 août 2013 21:23, "S Page" spage@wikimedia.org a écrit :
On Sun, Aug 18, 2013 at 7:11 AM, Jean-Frédéric < jeanfrederic.wiki@gmail.com> wrote:
What we achieved in the end is a big “Upload a file” (« Importer un fichier » in French) button on the French-language main page. [1] [2] Our rationale was that it is unreasonable to have people look for the tiny link in the left menu bar.
Any thoughts on this? Good, bad, ugly?
I think the Agora buttons look nicer than the jQuery UI classes, <span class="mw-ui-button mw-ui-primary mw-ui-big">Importer un fichier</span> But, commons doesn't load 'mediawiki.ui' by default, probably because it isn't using Echo yet. And Special:UploadWizard isn't using Agora.
-- =S Page software engineer on Editor Engagement Experiments
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
On Mon, Aug 19, 2013 at 12:43 PM, Benoît Evellin < benoit.evellin@wikimedia.fr> wrote:
Is there, anywhere, a documentation about the CSS classes used by the EE and E3 projects? This style or the other one: what does the guideline say?
Sadly https://www.mediawiki.org/wiki/Agora has no guideline as to when to use mw-ui-big, mw-ui-primary, mw-ui-constructive, etc.
We could split the prescriptive real-world "Do this with current code" from aspirational "We want the experience to be like this" design guide. But I would rather have a "Status" section on every design guide page anchoriong it to reality, saying what our skins and extensions currently implement and pointing to code in development. I've added this information to pages and others have removed it, probably because it's messy and disorganized; but so is the real world of MediaWiki 1.22wmf13. Maybe the Status section could be hidden by default so the design guide looks good (I'm not being snarky).
Regards, -- =S Page software engineer on Editor engagement experiments
On 08/20/2013 04:27 PM, S Page wrote:
On Mon, Aug 19, 2013 at 12:43 PM, Benoît Evellin <benoit.evellin@wikimedia.fr mailto:benoit.evellin@wikimedia.fr> wrote:
Is there, anywhere, a documentation about the CSS classes used by the EE and E3 projects? This style or the other one: what does the guideline say?
Sadly https://www.mediawiki.org/wiki/Agora has no guideline as to when to use mw-ui-big, mw-ui-primary, mw-ui-constructive, etc.
I've expanded documentation for the mediawiki.ui module at https://www.mediawiki.org/wiki/ResourceLoader/Default_modules#mediawiki.ui
We could split the prescriptive real-world "Do this with current code" from aspirational "We want the experience to be like this" design guide.
In general, I think the documentation should say how things really are. I.E. tell developers how to use the UX libraries to do real work.
If there is a requested change a team intends to work on, it should be added to a bug or issue tracker. That can link to a separate page clearly labelled as "brainstorming" or "proposed"
Matt Flaschen