[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pmf69tfn.fsf@meer.lwn.net>
Date: Wed, 05 Oct 2022 09:33:16 -0600
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Jani Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH RFC 0/5] docs: Improvements to our HTML output
Mauro Carvalho Chehab <mchehab@...nel.org> writes:
> I would play with the sidebar options used by Alabaster in order to
> try to make the TOC more useful.
Definitely worth doing; I'm not sure how much flexibility there is
there.
I'd *really* like to avoid carrying our own theme if at all possible...
The right solution might be to actually split the books apart and do the
intersphinx thing; I've not really looked into that at all.
> On a side note, one thing I miss on all default themes is a way to dynamically
> use dark mode. That's btw why I ended adding non-default support for
> 'sphinx_rtd_dark_mode' (which also requires an external package). At the time
> I added CSS/themes customization support to the build system, this was the only
> theme that allowed to switch to either dark/light mode. It would be really cool
> if Alabaster (or some other default themes) could honor the user's preference
> between light/dark modes.
Yeah, Alabaster doesn't seem to have that. Providing that ability in
conf.py shouldn't be *that* hard to do; it doesn't use that many colors,
though there might be a fair amount of CSS to override.
Thanks,
jon
Powered by blists - more mailing lists