From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: 'Thomas Monjalon' <thomas.monjalon@6wind.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] update css colours and shadows
Date: Mon, 15 Feb 2016 14:00:55 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612869530@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1573206.yIbr0ftlUT@xps13>
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Colours debate... ;)
The best bikeshed topic ever :D
Re: HyperLink Color
> May we keep a kind of red as the one in the logo?
Done, v2 uses #EF4E22 as in the logo
Re: Logo and padding
> I'm OK to give more space between the logo and the content,
> but not above the logo (which is just a waste IMHO).
Hmmm, to me it allows the logo to "breathe" in the space around it.
v2 compromises to have the space split between top and bottom of
the logo - see what you think.
Re: Shadows
> Why removing the shadow for the menu?
Re-worked to show only on the right hand side, not on the top.
See what you think.
Re: Menu shadow / lighting
> I really like this small light effect. Why removing?
> The flat trend?
Re-added, fixed shadow colours to suit the new colours.
Re: Nav Bar Colours
> But I don't like this hover color.
Hover is now orange instead of lighter purple.
> I think it's better to keep rounded corners at the bottom like above.
v2 leaves untouched.
Sent v2 patch just now, -Harry
next prev parent reply other threads:[~2016-02-15 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:24 Harry van Haaren
2016-02-12 15:46 ` Thomas Monjalon
2016-02-15 14:00 ` Van Haaren, Harry [this message]
2016-02-15 14:00 ` [dpdk-web] [PATCH v2] " Harry van Haaren
2016-02-18 18:05 ` Thomas Monjalon
2016-02-19 8:55 ` Van Haaren, Harry
2016-02-19 11:26 ` Thomas Monjalon
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=E923DB57A917B54B9182A2E928D00FA612869530@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).