From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org
Cc: Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [RFC PATCH v2] docs: rework "Working with the development community"
Date: Wed, 26 Jul 2023 13:30:58 -0600 [thread overview]
Message-ID: <87edku8o7h.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230726184939.3118350-1-costa.shul@redhat.com>
Costa Shulyupin <costa.shul@redhat.com> writes:
> Mission: Make the documentation more readable, organized and maintainable.
>
> NB: no information content is lost of changed on the rendered top page.
>
> This patch demonstrates rework of the only the first section
> of the top page for review. The proposal is to rework all sections.
>
> Summary of changes:
> - Heading "Working with the development community" is converted into
> branch of toctree and visually moved after the text
> "The essential guides for interacting ..."
> - toctree list is split into separated file. Please don't worry, the
> content of the list is incorporated to the top page because of
> `:maxdepth: 2`
> - vertical bar '|' add empty line for better visual distribution
I will repeat. I do not support carving useful stuff out of the front
page in this way. The front page does not exist just to make a
nice-looking sidebar.
> Technical explanations:
> Template {{ toctree(maxdepth=3) }} in
> Documentation/sphinx/templates/kernel-toc.html
> uses directives toctree and doesn't use sections on the top page
> Documentation/index.rst
> to generate expandable toc on the sidebar.
>
> BTW, other template {{ toc }} uses only sections, and doesn't
> use directives toctree.
*This* is where the problem lies. I have started looking at it again,
but digging deep into the Sphinx code can be painful at times.
jon
prev parent reply other threads:[~2023-07-26 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:31 [RFC PATCH] rework top page and organize toc on the sidebar Costa Shulyupin
2023-07-24 21:21 ` Jonathan Corbet
2023-07-25 3:04 ` Randy Dunlap
2023-07-26 5:55 ` Costa Shulyupin
2023-07-26 6:03 ` Randy Dunlap
2023-07-26 13:54 ` Jonathan Corbet
2023-07-26 18:49 ` [RFC PATCH v2] docs: rework "Working with the development community" Costa Shulyupin
2023-07-26 19:30 ` Jonathan Corbet [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=87edku8o7h.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@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