From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Antonin Godard" <antonin.godard@bootlin.com>
Subject: Re: [PATCH RFC] sphinx-static/theme_overrides.css: switch to a fixed width documentation
Date: Mon, 20 Apr 2026 14:14:13 +0200 [thread overview]
Message-ID: <DHXZ2GGKEOL2.3HHYILCUSYA9N@bootlin.com> (raw)
In-Reply-To: <20260202-fixed-width-html-v1-1-e987deb9926d@bootlin.com>
On Mon Feb 2, 2026 at 11:47 AM CET, Antonin Godard wrote:
> Change the css rules of our theme to have a fixed-width documentation
> instead of it taking the full width of the page. I believe this makes it
> much more readable compared to having long lines with few line returns,
> especially on high-resolution displays. Set the width to 1000px instead
> of the previous 800px, which felt slightly too thin.
>
> I think the removed comment here does not make that much sense for us.
> It was added by commit 0c1e108bc6c4 ("sphinx: add CSS theme override"),
> and I believe is a simply copy and paste of what was is set in the Linux
> kernel, added by commit 9abaf979abb2 ("doc-rst: customize RTD theme,
> table & full width") [1].
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9abaf979abb2
A preview of this patch can be seen at
https://docs.yoctoproject.org/next/index.html.
Any feedback appreciated! I think the docs are more readable like this.
The only drawbacks I would see are:
- Large tables are a bit less readable (but we only have a few: in the release
notes and on the list of supported features, IIRC).
- Detailed images are not as readable (but can be clicked to be seen fully).
Thanks,
Antonin
prev parent reply other threads:[~2026-04-20 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 10:47 [PATCH RFC] sphinx-static/theme_overrides.css: switch to a fixed width documentation Antonin Godard
2026-04-20 12:14 ` Antonin Godard [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=DHXZ2GGKEOL2.3HHYILCUSYA9N@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.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