qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [qemu-web PATCH 5/7] Simplify and restructure the page footer
Date: Fri, 23 Oct 2020 17:46:00 +0100	[thread overview]
Message-ID: <20201023164600.GC463062@redhat.com> (raw)
In-Reply-To: <54f37d84-a66e-bbfa-b410-2dba44d88ac9@redhat.com>

On Fri, Oct 23, 2020 at 05:46:49PM +0200, Paolo Bonzini wrote:
> On 23/10/20 17:29, Daniel P. Berrangé wrote:
> > +	<div id="external-links">
> >  		<ul class="style">
> > -			<li><a href="{{ relative_root }}/">Home</a></li>
> > -			<li><a href="{{ relative_root }}/download">Download</a></li>
> > -			<li><a href="{{ relative_root }}/conservancy/">Conservancy / Committee</a></li>
> > -			<li><a href="http://qemu-advent-calendar.org">QEMU advent calendar</a></li>
> > -		</ul>
> > -		<ul class="style">
> > -			<li><a href="{{ relative_root }}/contribute">Contribute</a></li>
> > -			<li><a href="{{ relative_root }}/contribute/report-a-bug">Reporting a bug</a></li>
> > -			<li><a href="https://wiki.qemu.org/Documentation/GettingStartedDevelopers">New contributors</a></li>
> > -			<li><a href="https://wiki.qemu.org/Contribute/SubmitAPatch">Submitting a patch</a></li>
> > -			<li><a href="https://wiki.qemu.org/Contribute/FAQ">Contributor FAQ</a></li>
> > -		</ul>
> 
> I would rather keep this column, the idea is that this information can
> be found with a quick Ctrl-F "bug" or "Ctrl-F "faq".

If there are useful links that are hidden such that people have to use
"Ctrl-f <term>" to search for them, then I think we've failed at design
already.

I'm inclined to do some work on the top level index page to make these
things be prominent links you can see without scrolling or searching
when hitting the http://qemu.org/ front page.

IMHO the front page has way too much real estate taken up with the
screenshots and big headings, and very little useful content right
now. On my laptop 50% of the vertical space is the top header nav
bar, the huge "QEMU" heading and then the subheading. The other
50% of vertical space is the screenshots. The most interesting
content on the front page is the summary of latest releases, but
that's off screen. I'll have a play with tweaking the layout to
improve this.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-10-23 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 15:29 [qemu-web PATCH 0/7] Tweaks to page footer and add "edit page" links Daniel P. Berrangé
2020-10-23 15:29 ` [qemu-web PATCH 1/7] Convert files to UNIX line endings Daniel P. Berrangé
2020-10-23 15:29 ` [qemu-web PATCH 2/7] gitlab: introduce a CI job to publish the site content Daniel P. Berrangé
2020-10-23 15:29 ` [qemu-web PATCH 3/7] make all links be relative to the root Daniel P. Berrangé
2020-10-23 15:29 ` [qemu-web PATCH 4/7] Make page header nav narrower Daniel P. Berrangé
2020-10-23 15:29 ` [qemu-web PATCH 5/7] Simplify and restructure the page footer Daniel P. Berrangé
2020-10-23 15:46   ` Paolo Bonzini
2020-10-23 16:46     ` Daniel P. Berrangé [this message]
2020-10-23 17:19       ` Paolo Bonzini
2020-10-23 15:29 ` [qemu-web PATCH 6/7] Add link to "edit this page" for all pages Daniel P. Berrangé
2020-10-23 15:47   ` Paolo Bonzini
2020-10-23 16:19     ` Daniel P. Berrangé
2020-10-23 17:07       ` Paolo Bonzini
2020-10-23 15:29 ` [qemu-web PATCH 7/7] Add a CONTRIBUTING.md file as guidance for contributors Daniel P. Berrangé
2020-10-23 15:50   ` Paolo Bonzini

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=20201023164600.GC463062@redhat.com \
    --to=berrange@redhat.com \
    --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 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).