TLDR, if your team has been using progressive and constructive buttons,
There is a task on button consolidation (
https://phabricator.wikimedia.org/T110555) that is being blocked by teams
who are using progressive and constructive buttons. This task is also
blocking another task (https://phabricator.wikimedia.org/T109915).
We (standardization team and community) have come to consensus
on consolidating progressive (blue) and constructive (green) buttons (
https://phabricator.wikimedia.org/T110555). We've decided to stick with
using only progressive color buttons due to a few reasons such as:
1. "we've had confusions from developers and community members in
understanding when and where to use constructive vs. progressive. For our
users to learn the association of constructive button being the last action
in a process and progressive being the in-betweens, it "requires [the
pattern] to be applied consistently to work" - Isarra
2. "in certain complex processes, it's hard to tell which would be the
last step." - Pau
There are many factors why these complications can happen, but looking at
the realistic resources we have to validate the effect it has on our users,
we went back and consider the original intent of use of these buttons. Feel
free to read more about it here (
Help us move forward in commenting on the task (
https://phabricator.wikimedia.org/T110555). Thank you!
Discussion on design list
Discussion on Phabricator
The standardization team is currently working on the Wikimedia User Interface style guide, where it will be a one-stop shop for all design resources and specs in the future. But for now, you can obtain these updated resources from the Design Resources section of our team's wiki.
UI elements for use by designers / others (Sketch • how to use gif) and specs for developers (WMFLabs • LESS file);
Three ways of using our icon library -- SVG, SVG sprite, and Icon font.
We will keep updating this thread as more resources become available and updated.
My name is Vikram Aditya, and I am currently a Pre-Final year Bachelors of
Design student at IIT Guwahati.
I wish to apply for the position of a Design Internship at the Wikimedia
Foundation during the summer of 2016. If I have reached the wrong place, it
would be very kind of you to guide me in the right direction.
Having interned at Interface Sense <http://interfacesense.com/> as a UX
Designer and at Cobalt.io <http://cobalt.io/> as a remote graphic design
intern along with having worked on several design projects, I am well
versed with the User Experience, Typography, Visual Communication, User
Study, Heuristic Evaluation and Front-End Development. I also have been
passionate about Interaction Design and Human Computer Interaction and have
carried out several projects from this domain as a part of my course. Recently
I have taken up a project on organic interfaces at the Embedded Interaction
Lab <http://embeddedinteractions.com/> where I am apart of a team trying to
visualise new interactions with shape changing displays in collaboration
Please find my curriculum vitae at
My portfolio link is: http://vikramadityadesign.com/
Please let me know if my work and interests match with the profile that you
might be looking for.
| *Vikram Aditya*
*| *Pre-Final Year Student (B.Des)
*|* Department of Design
*|* Indian Institute of Technology Guwahati
| Portfolio: http://vikramadityadesign.com/
*| *+91 8011035410 | Alternate Email : *vikramaditya(a)iitg.ernet.in
Sent with MailTrack
We wouldn't want to use web components for the reasons you mentioned and
polymer because it uses shadow DOM, where you cannot share css styles.
What would be great is webcomponent-like custom elements that share css,
that's why webcomponents.js <http://webcomponents.org/polyfills/> is used in
this library <http://wikimedia-ui.wmflabs.org/>. It will be much more
accessible for a lot more users if we managed to do similar things to OOjs
UI components with a more approachable language for uses in and out of wiki
like <wiki-icon icon="star" color="green"></wiki-icon>
On Sun, Jan 10, 2016 at 2:54 PM, Prateek Saxena <psaxena(a)wikimedia.org>
> On Wed, Nov 11, 2015 at 1:59 PM, S Page <spage(a)wikimedia.org> wrote:
> > Sure, but how cool would it be if OOjs UI were expressible as
> > WebComponent-ish things…
> I have been considering the WebComponent approach since before we
> decided OOjs UI to be our go to UI library, but it obviously isn't
> ready to be our main UI technology. Iteratively adding a WebComponent
> layer to OOjs UI shouldn't be hard but I have mixed feelings about it
> * Lack of support . We'll still need parser tags to consistently
> support these tags.
> * Maintainability.
> * Choice of polyfill and/or library, brick/polymer.
> It does solve the UI prototyping problem, but I wonder if its worth the
>  I am super excited about WebComponents but want to hold myself back.
>  http://caniuse.com/#search=web%20components
> Design mailing list
Did you see this before? http://wikimedia-ui.wmflabs.org ..a simple way
to get the code for the graphics you want. Very neat. Helps us all build
a clean and visiually unified look of pages.
I spotted it in the In the recent discovery and reading showcae . Bravo
and thanks to May Tee-Galloway :)