From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] docs: Improvements to our HTML output
Date: Sat, 15 Oct 2022 19:41:35 +0700 [thread overview]
Message-ID: <2f9f1cab-1053-db07-68aa-724741356fbb@gmail.com> (raw)
In-Reply-To: <20221013172918.846856-1-corbet@lwn.net>
On 10/14/22 00:29, Jonathan Corbet wrote:
> Sphinx has a theming mechanism for HTML rendering. Since the kernel's
> adoption of Sphinx, we have been using the "Read The Docs" theme — a choice
> made in a bit of a hurry to have *something* while figuring out the rest.
> RTD is OK, but it is not hugely attractive, requires the installation of an
> extra package, and does not observe all of the Sphinx configuration
> parameters. Among other things, that makes it hard to put reasonable
> contents into the left column in the HTML output.
>
> The Alabaster theme is the default for Sphinx installations, and is bundled
> with Sphinx itself. It has (IMO) nicer output and gives us the control
> that we need.
>
I don't see how switching theme will solve the left column problem. Are
there any customizations on that column that are planned?
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-10-15 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 17:29 Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 1/6] docs: Switch the default HTML theme to alabaster Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 2/6] docs: tweak some Alabaster style parameters Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 3/6] docs: update sphinx.rst to reflect the default theme change Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 4/6] docs: sphinx-pre-install: don't require the RTD theme Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 5/6] docs: improve the HTML formatting of kerneldoc comments Jonathan Corbet
2022-10-13 17:29 ` [PATCH v3 6/6] docs: decruft Documentation/conf.py Jonathan Corbet
2022-10-15 12:41 ` Bagas Sanjaya [this message]
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=2f9f1cab-1053-db07-68aa-724741356fbb@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®