All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pine, Kathryn ElaineX" <kathryn.elainex.pine@intel.com>
To: Derick Montague <Derick.Montague@ibm.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: GUI Component Library
Date: Mon, 2 Dec 2019 22:08:17 +0000	[thread overview]
Message-ID: <FD0BD680739BFC41807C96BD23118BB131A69B@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <OF518FB33F.0A608011-ON002584BF.0046C766-002584BF.005B81EB@notes.na.collabserv.com>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

>The goal of the style guide is to document our consensus. It would be helpful to agree on some of the foundational aspects of the application to make the concept process easier.



My proposal is that we work towards a vision with concepts for the overall site prior to getting into the details, as a method for consensus building. Our work will be the best if we agree on a look that encompasses a shared vision for the entire UI, not just individual elements. I’ve shared a few example websites that from my perspective, look like a happy medium of both our styles, and expect we can find more good examples if we want to go down this path.



I think we have the opportunity – leaning on the collaborative strengths that we can all bring – to combine what we have each been working on to make something even better. But it will mean being willing to compromise some of our style preferences to agree on a shared vision. Is there interest on working towards this vision together? It seems like a good time given the rebuilding with VueJS.



If we can agree on the big picture, creating a style guide or choosing a design library will be much easier as we’ll have consensus reflecting that shared vision.



How about we discuss in this week's GUI Design work group meeting?



Suggested topics:

  *   Transition to VueJS
  *   Goals & Improvements
     *   Style goals – can we unify to a single style preference?
     *   Design library vs Style guide
  *   (If time)
     *   Non-style contributions – process for logging issues
     *   Current work in pipeline





[-- Attachment #2: Type: text/html, Size: 10519 bytes --]

  reply	other threads:[~2019-12-02 22:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 21:47 GUI Component Library Derick Montague
2019-11-20 22:36 ` Jandra A
2019-11-20 22:56   ` Pine, Kathryn ElaineX
2019-11-21  1:45     ` Derick Montague
2019-11-22 15:22 ` Pine, Kathryn ElaineX
2019-11-25 21:03   ` Derick Montague
2019-11-25 21:17     ` Jandra A
2019-11-26 21:19     ` Pine, Kathryn ElaineX
2019-11-27 16:39       ` Derick Montague
2019-12-02 22:08         ` Pine, Kathryn ElaineX [this message]
2019-12-03 17:31           ` Jandra A
2019-12-03 21:00             ` Pine, Kathryn ElaineX
2019-12-03 20:34           ` Derick Montague
2019-12-03 21:00             ` Pine, Kathryn ElaineX
2019-11-27 18:24       ` James Feist
2019-11-27 18:39         ` Derick Montague

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FD0BD680739BFC41807C96BD23118BB131A69B@ORSMSX113.amr.corp.intel.com \
    --to=kathryn.elainex.pine@intel.com \
    --cc=Derick.Montague@ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.