From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] my attempt at new QEMU website
Date: Thu, 20 Oct 2016 14:23:27 +0100 [thread overview]
Message-ID: <20161020132327.GQ12145@redhat.com> (raw)
In-Reply-To: <96ff6a47-57cb-ec2a-7864-84c6389efe1f@redhat.com>
On Thu, Oct 20, 2016 at 02:16:37PM +0200, Paolo Bonzini wrote:
>
>
> On 20/10/2016 08:43, Thomas Huth wrote:
> > On 19.10.2016 12:53, Paolo Bonzini wrote:
> >> Hi all,
> >>
> >> another small PSA. :) I have created a small but hopefully useful
> >> example of a new QEMU website at http://qemu-bonzini.rhcloud.com/. The
> >> site aims at providing and also a home for blog posts about QEMU.
> >
> > Looks good to me! Two comments, though:
> >
> > - The main font color is not black, but rather some dark grey. I think
> > I'd rather change that to something darker (either black or a darker
> > grey) instead - there are people who have problems with low contrasts,
> > and especially the "What is QEMU?" section with the light grey
> > background might be hard to read for them.
>
> Reload for a surprise. :)
I'm not a fan of the huge page in the background - even with it faded
out it still distracts from the content above it. The bright red banner
is a bit too brash too and some of the different colour shades clash.
I mocked up a variant on your styling to illustrate a potential
alternative approach:
https://berrange.com/~dan/qemu/index.html
There's essentially only 2 colors used there - the orange from the
QEMU logo is used for links when you hover/click them. That orange
then has lightness value reduced, so give the darker orange for
header and non-active links. That ensures the relative color mix
between the two is consistent, avoiding clashing color.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-10-20 13:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 10:53 [Qemu-devel] my attempt at new QEMU website Paolo Bonzini
2016-10-19 11:02 ` Daniel P. Berrange
2016-10-19 11:36 ` Alexander Graf
2016-10-19 11:46 ` Paolo Bonzini
2016-10-19 12:07 ` Lluís Vilanova
2016-10-19 12:19 ` Paolo Bonzini
2016-10-20 2:14 ` Fam Zheng
2016-10-20 12:06 ` Paolo Bonzini
2016-10-20 6:43 ` Thomas Huth
2016-10-20 12:16 ` Paolo Bonzini
2016-10-20 13:23 ` Daniel P. Berrange [this message]
2016-10-21 13:34 ` Daniel P. Berrange
[not found] <mailman.11411.1476878784.22740.qemu-devel@nongnu.org>
2016-10-19 19:54 ` Programmingkid
2016-10-19 20:46 ` Paolo Bonzini
2016-10-20 2:05 ` Fam Zheng
2016-10-20 8:30 ` Daniel P. Berrange
2016-10-20 12:56 ` Paolo Bonzini
2016-10-21 2:10 ` Programmingkid
2016-10-21 5:23 ` Stefan Weil
2016-10-21 9:22 ` Paolo Bonzini
2016-10-20 13:57 ` Programmingkid
2016-10-20 14:02 ` Daniel P. Berrange
2016-10-20 14:47 ` Peter Maydell
2016-10-20 15:05 ` Eric Blake
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=20161020132327.GQ12145@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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.