From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: QEMU wiki theme table of contents changes
Date: Fri, 15 Nov 2024 08:54:25 +0000 [thread overview]
Message-ID: <ZzcMQeHfBTm2iEsc@redhat.com> (raw)
In-Reply-To: <CAJSP0QUkfSO3uXPjZCxNfCfVwwWBBy6u5a=PjqqnMZSxE95YpA@mail.gmail.com>
On Thu, Nov 14, 2024 at 02:04:35PM -0500, Stefan Hajnoczi wrote:
> On Thu, 14 Nov 2024 at 05:51, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > Looking at
> >
> > https://wiki.qemu.org/ChangeLog/9.2
> >
> > I'm thinking that I'm sure there used to be a table of contents present
> > at the top of pages, but none is to be seen..... until I eventually
> > discover that there's a bare noticable, fully collapsed ToC in the left
> > hand nav panel below all the general wiki nav links, partially off the
> > bottom of the page :-(
> >
> > If going to https://wiki.qemu.org/Special:Preferences, "Appearance" and
> > selecting "Vector legacy (2010)" as the "Skin" instad of "Vector (2022)"
> > then the full ToC re-appears at the top of page in the main body content.
> >
> > I'm presuming this style change was triggered by a software upgrade that
> > was done on the wiki at some point.
> >
> > IMHO this is quite a significant visual/usability regression.
> >
> > On wikipedia, they do have the same theme, with ToC in the left hand
> > panel, but their ToC is expanded by default, and there's no other general
> > navigation in the left hand panel that's displacing the ToC off the bottom
> > of the page. That is fairly effective as a layout.
> >
> > We can do something to the QEMU skin to improve this ? Swapping order
> > of the ToC & general nav blocks in the left hand panel would be a
> > improvement, as well making it expand at least 1 further level by
> > default.
> >
> > If we're going to have background colour set for the general nav block,
> > we should also probably do similar for the ToC nav block to make it
> > visually stand out to the same degree.
>
> Yes, that sounds good. The quickest would be for you to:
> 1. Run https://hub.docker.com/_/mediawiki/ in a container on your machine.
> 2. Adjust the theme CSS until you are happy.
> 3. Send me the tweaks and I will apply them to wiki.qemu.org.
Is the current QEMU mediawiki code (or just theme) published anywhere
that I can base work off ?
With 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 :|
next prev parent reply other threads:[~2024-11-15 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 10:50 QEMU wiki theme table of contents changes Daniel P. Berrangé
2024-11-14 19:04 ` Stefan Hajnoczi
2024-11-15 8:54 ` Daniel P. Berrangé [this message]
2024-11-15 19:21 ` Stefan Hajnoczi
2024-11-15 19:38 ` Daniel P. Berrangé
2024-11-19 19:54 ` Stefan Hajnoczi
2024-11-21 15:48 ` Daniel P. Berrangé
2024-12-04 21:26 ` Stefan Hajnoczi
2024-12-05 11:56 ` Daniel P. Berrangé
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=ZzcMQeHfBTm2iEsc@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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).