From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] my attempt at new QEMU website
Date: Wed, 19 Oct 2016 12:02:34 +0100 [thread overview]
Message-ID: <20161019110234.GN11194@redhat.com> (raw)
In-Reply-To: <27375f5d-5810-b23e-bffa-83f1d18b34d5@redhat.com>
On Wed, Oct 19, 2016 at 12:53:55PM +0200, 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.
>
> The site resides in a single git tree, so that requests to modify the
> pages (and even blog posts :)) can be posted to qemu-devel as usual.
>
> The blog post in there is dummy, and the "blog" link will be removed
> from navigation until there's a first post, if the site goes online.
>
> The site is designed to live together with the wiki and provide a
> migration path for qemu-project.org, from the wiki to a standalone
> website. For example:
>
> - http://qemu-bonzini.rhcloud.com/Download redirects to the new page
> http://qemu-bonzini.rhcloud.com/download
>
> - http://qemu-bonzini.rhcloud.com/BiteSizedTasks redirects to the wiki
> page http://wiki.qemu-project.org/BiteSizedTasks
>
> - http://qemu-bonzini.rhcloud.com/foobar is a 404 page
>
> Impressions, ideas and lart-ing for my feeble attempts at Javascript
> (now I understand why people are so keen on stackoverflow!) and graphic
> design are welcome. (Yes, the icons in the homepage are not definitive).
My main question is about the styling + logo. We have a logo for QEMU,
but neither the old website nor your new website use it.
http://wiki.qemu.org/Logo
It has a quite distinct black + orange colourscheme, which IMHO doesn't
fit with the greenish colour scheme you've used here.
Do we still like that logo ? If so, we should use it, and align the
website colour scheme with that logo colourscheme, so we have a consistent
brand style.
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-19 11:02 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 [this message]
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
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=20161019110234.GN11194@redhat.com \
--to=berrange@redhat.com \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.