I love the idea of having a live style guide page! I don’t see why we couldn’t do something like that with our gaia-components page:
http://gaia-components.github.io/gaia-components/ <http://gaia-components.github.io/gaia-components/> -Justin > On Oct 28, 2015, at 2:52 PM, Patryk Adamczyk <[email protected]> wrote: > > Hello, consistency in user experience is definitely a benefit but whatever > solution we come up, it would be great if we can think of the dev and mozilla > community as well. If you take a look at this example: > https://www.lightningdesignsystem.com/ > <https://www.lightningdesignsystem.com/> everything is live, the component > code is visual, it can easily be downloaded and hacked by the user. > > So there is also another part to this, and that would to have it sit in a > live styleguide. > Imagine if the components can be in github and a single change in github > would instantly update: > + master and every FXOS app > + style guide website > > That would be amazing! > > It would really echo the ideas of focus and dynamic efficiency. > > -P > > >> On Oct 28, 2015, at 1:02 PM, Justin D'Arcangelo <[email protected] >> <mailto:[email protected]>> wrote: >> >>> >>> On Oct 28, 2015, at 4:33 AM, Wilfred Mathanaraj <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi all >>> >>> In the past we had a proposal to use web-components to bring uniformity to >>> the UX on FxOS - we did a partial implementation of this and it has left >>> our UX with an “unfinished” look and feel. >>> Moving forward we want to have a very uniform UX across all our core apps. >>> We also want to make this uniform experience available to contributors. >>> >>> Having common components to achieve this will also help with the following: >>> >>> 1. UX to easily manage UX changes >>> 2. Engineering to reduce code size by using these common components >>> 3. QA to reduce their testing >>> >>> One of the methods we identified is web-components and there have been some >>> concerns raised with : >>> >>> 1. time taken to implement each component >>> 2. possible performance impacts web-components calls may have. >>> >> >> FWIW, the *entire* UI in the Music NGA re-write was built using web >> components. We used a combination of the gaia-components as well as some >> app-specific custom elements. I don’t believe either of these concerns are >> valid anymore. We were able to throw together web components very quickly >> when we needed to. Also, we are not seeing any noticeable performance impact >> from our heavy use of web components. >> >> I saw someone else noted a concern about the Shadow DOM API not being etched >> in-stone yet, which is a valid point. However, we can also make use of the >> excellent work Wilson has put into the base “gaia-component” class. This >> base class allows us to work around any gaps in the platform and also >> provides a thin layer of abstraction between the component and the platform. >> So, if things change from the API standpoint, we should (hopefully) be able >> to just address those changes in the base “gaia-component” class. >> >> I am hugely in favor of continuing down the web components route. Even just >> from a maintainability standpoint, web components were able to encapsulate >> all the UI complexity in the Music NGA app which kept each view’s >> HTML/CSS/JS code very clear and concise. >> >> -Justin >> >>> We are currently trying to identify other possibilities to achieve such a >>> uniform implementation - if any of you have any proposals please feel free >>> to reach out to Rob, Hema, or myself. >>> >>> BR >>> Wilfred >>> >>> >>> >>> --- >>> FxOS Product Management >>> Mozilla Corp., UK >>> >>> >>> >>> >>> _______________________________________________ >>> dev-fxos mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.mozilla.org/listinfo/dev-fxos >>> <https://lists.mozilla.org/listinfo/dev-fxos> >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] <mailto:[email protected]> >> https://lists.mozilla.org/listinfo/dev-fxos >> <https://lists.mozilla.org/listinfo/dev-fxos> > --- > Patryk Adamczyk, R.G.D. > Design Manager - Visual Design Firefox OS > Mozilla Corporation >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
