From: Randy Dunlap <rdunlap@infradead.org>
To: "Jonathan Corbet" <corbet@lwn.net>,
"Costa Shulyupin" <costa.shul@redhat.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
"open list:RUST" <rust-for-linux@vger.kernel.org>
Subject: Re: [RFC PATCH] rework top page and organize toc on the sidebar
Date: Mon, 24 Jul 2023 20:04:59 -0700 [thread overview]
Message-ID: <9fa8e67e-e46b-074d-8406-bfd11303e95f@infradead.org> (raw)
In-Reply-To: <87ila9atuk.fsf@meer.lwn.net>
On 7/24/23 14:21, Jonathan Corbet wrote:
> Costa Shulyupin <costa.shul@redhat.com> writes:
>
>> 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.
>>
>> Summary of changes:
>> - split top page index.rst to several pages
>> - convert sections of Documentation/index.rst to hierarchical toctree
>> - vertical bars '|' add empty lines
>>
>> Benefits:
>> - collapsed toc is just seven short lines length
>> - toc is expandable
>>
>> References:
>> - https://www.sphinx-doc.org/en/master/development/templating.html#toctree
>> - https://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#directive-toctree
>> - https://www.sphinx-doc.org/en/master/development/templating.html#toc
>> - https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#sections
>> - https://sphinx-rtd-theme.readthedocs.io/
>
> What is the purpose of all these links in a patch changelog?
>
> This patch is somewhat difficult to apply, as a result of:
>
>> Content-Type: text/plain; charset=true
I didn't have any problem applying and testing it.
> But the real problem is that you seem to have ignored my last message.
> The purpose of the front page isn't to create a nice-looking sidebar, it
> is the entry point to our documentation as a whole. I am all for a
> better sidebar, but this is not the way to do it.
Regardless of what the purpose of the front page is, I prefer this one
from Costa. The other one is a huge mess.
--
~Randy
next prev parent reply other threads:[~2023-07-25 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:31 Costa Shulyupin
2023-07-24 21:21 ` Jonathan Corbet
2023-07-25 3:04 ` Randy Dunlap [this message]
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
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=9fa8e67e-e46b-074d-8406-bfd11303e95f@infradead.org \
--to=rdunlap@infradead.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--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