There's been a lot of discussion in some meetings around "UI
Standardization". Here's my view I've expressed:

   1. I will always be in support of designers having whatever tool is
   needed for them to be able to mockup their work in HTML/CSS. I believe that
   working in this format is beneficial to communication, collaboration and
   quality.
   2. The kinds of controls that can be expressed in plain HTML/CSS is a
   fraction of what can be expressed using OOjs UI or any other
   JavaScript-based approach. Even simple things, like designing a type-ahead
   feature, can't be done using HTML/CSS alone.

This leads me to feel strongly that this while it might be cool for the
production library (OOjs UI) to be used in some way to make the designer's
work easier, it's not required and in no way should the designer's tool
direct the implementation of OOjs UI or any production software.

- Trevor

On Wed, Nov 4, 2015 at 5:39 AM, Bartosz Dziewoński <[email protected]>
wrote:

> It's neat indeed, but…
>
>
> On 2015-11-04 13:59, Moushira Elamrawy wrote:
>
>> Helps us all build a clean and visiually unified look of pages.
>>
>
> That page does not look visually unified with any of the Wikipedia pages
> I've seen. In fact, it just looks like Bootstrap.
>
> Can't we focus on a *single* styling guide instead of creating more
> incompatible ones? :(
>
> --
> Bartosz Dziewoński
>
> _______________________________________________
> Design mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/design
>
_______________________________________________
Design mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/design

Reply via email to