From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>, Sadiya Kazi <sadiyakazi@google.com>
Cc: brendanhiggins@google.com, davidgow@google.com,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: New theme - Alabaster for Kernel Documentation
Date: Thu, 19 Jan 2023 14:29:21 -0700 [thread overview]
Message-ID: <87r0vq6wni.fsf@meer.lwn.net> (raw)
In-Reply-To: <c00df839-9429-891b-5682-3dbc2d6edbbe@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> Konstantin, would it be possible for you to add "DOCS_THEME=sphinx_rtd_theme"
> for the "latest" kernel documentation builds until the new default theme
> becomes good enough for most people? That is if Jon agrees.
> For the "next" builds, alabaster theme should be OK, and easier for us to
> compare the two themes.
I'd prefer to avoid this if possible. In the end, though, what
kernel.org does isn't my decision, of course... but if the Alabaster
mode is really that bad, we should either fix it or just revert the
change. I'll try to dig into the sidebar generation a bit, but time is
scarce.
Before going too far, what exactly is the desired sidebar experience
here? I find the RTD approach, which keeps all of the top-level entries
there, to be severely messy and would prefer not to reproduce it. Of
course, some of that reflects the still-messy nature of our top-level
Documentation/ directory, another thing I'd like to fix.
Thanks,
jon
next prev parent reply other threads:[~2023-01-19 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 4:25 New theme - Alabaster for Kernel Documentation Sadiya Kazi
2023-01-19 4:00 ` Akira Yokosawa
2023-01-19 21:29 ` Jonathan Corbet [this message]
2023-01-19 21:46 ` Konstantin Ryabitsev
2023-01-19 21:55 ` Jonathan Corbet
2023-01-19 22:02 ` Konstantin Ryabitsev
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=87r0vq6wni.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=kunit-dev@googlegroups.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