linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>, Sadiya Kazi <sadiyakazi@google.com>
Cc: linux-doc@vger.kernel.org, David Gow <davidgow@google.com>
Subject: Re: [PATCH RFC] docs: Add more information to the HTML sidebar
Date: Fri, 20 Jan 2023 08:19:02 -0700	[thread overview]
Message-ID: <8735855j4p.fsf@meer.lwn.net> (raw)
In-Reply-To: <fa426691-c76a-8ab0-4975-6edacc9cb247@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

>>> Thoughts?  Is this headed in the right direction?  This view of the TOC
>>> is readily available from Sphinx; if we want something else it's going
>>> to be rather more work.
>
> I think this looks like the right direction. But how far do you want to
> mimic RTD's sidebar???

Well ... that is kind of my question for all of the folks who are
unhappy with the current sidebar.  What would you like to see there?

Things like sidebar width, whether bullets are used (I'd deliberately
taken them out as excess noise), which text is which color, etc. are all
just CSS; we can paint that shed any color we like.  The harder part is
deciding which information we want to have there in the first place.  So
... is the set of links shown in the new sidebar close to what we
want...  too much stuff?  Something missing?

Thanks,

jon

  reply	other threads:[~2023-01-20 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20  0:11 [PATCH RFC] docs: Add more information to the HTML sidebar Jonathan Corbet
2023-01-20  2:54 ` Bagas Sanjaya
2023-01-20 13:38 ` Sadiya Kazi
2023-01-20 14:09   ` Akira Yokosawa
2023-01-20 15:19     ` Jonathan Corbet [this message]
2023-02-03  2:37       ` Akira Yokosawa
2023-02-03  4:29         ` Sadiya Kazi
2023-01-23  0:05     ` Akira Yokosawa

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=8735855j4p.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=davidgow@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=sadiyakazi@google.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).