From: Carlos Bilbao <bilbao@vt.edu>
To: Randy Dunlap <rdunlap@infradead.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
alex.gaynor@gmail.com, wedsonaf@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@samsung.com,
aliceryhl@google.com,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1 RESEND] docs: Include simplified link titles in main page's index
Date: Sun, 10 Dec 2023 19:58:19 -0600 [thread overview]
Message-ID: <77b25d0b-ceb4-4589-bf40-ff464e2a6b7f@vt.edu> (raw)
In-Reply-To: <9b52c145-7466-4e81-a911-25f472c2a2ea@infradead.org>
On 12/10/23 7:41 PM, Randy Dunlap wrote:
> Hi Carlos,
>
> On 12/10/23 17:20, Carlos Bilbao wrote:
>> Include simplified link titles in the main page's documentation index to
>> enhance website's readability and UX. Update the text that directs users to
>> various documents without changing the actual titles chosen by the authors.
>>
>> Signed-off-by: Carlos Bilbao <bilbao@vt.edu>
>> ---
>> Documentation/index.rst | 50 ++++++++++++++++++++---------------------
>> 1 file changed, 25 insertions(+), 25 deletions(-)
>>
>> diff --git a/Documentation/index.rst b/Documentation/index.rst
>> index 9dfdc826618c..be395d0a4318 100644
>> --- a/Documentation/index.rst
>> +++ b/Documentation/index.rst
>> @@ -22,10 +22,10 @@ community and getting your work upstream.
>> .. toctree::
>> :maxdepth: 1
>>
>> - process/development-process
>> - process/submitting-patches
>> + Development process <process/development-process>
>> + Submitting patches <process/submitting-patches>
>> Code of conduct <process/code-of-conduct>
>> - maintainer/index
>> + Maintainer handbook <maintainer/index>
>> All development-process docs <process/index>
>>
>>
>> @@ -38,10 +38,10 @@ kernel.
>> .. toctree::
>> :maxdepth: 1
>>
>> - core-api/index
>> - driver-api/index
>> - subsystem-apis
>> - Locking in the kernel <locking/index>
>> + Core API <core-api/index>
>> + Driver implementation API <driver-api/index>
>> + Subsystems <subsystem-apis>
>> + Locking <locking/index>
>>
>> Development tools and processes
>> ===============================
>> @@ -51,15 +51,15 @@ Various other manuals with useful information for all kernel developers.
>> .. toctree::
>> :maxdepth: 1
>>
>> - process/license-rules
>> - doc-guide/index
>> - dev-tools/index
>> - dev-tools/testing-overview
>> - kernel-hacking/index
>> - trace/index
>> - fault-injection/index
>> - livepatch/index
>> - rust/index
>> + Licensing rules <process/license-rules>
>> + Writing documentation <doc-guide/index>
>> + Development tools <dev-tools/index>
>> + Testing <dev-tools/testing-overview>
>> + Hacking <kernel-hacking/index>
>> + Tracing <trace/index>
>> + Fault injection <fault-injection/index>
>> + Livepatching <livepatch/index>
>> + Rust <rust/index>
>>
>>
>> User-oriented documentation
>> @@ -72,11 +72,11 @@ developers seeking information on the kernel's user-space APIs.
>> .. toctree::
>> :maxdepth: 1
>>
>> - admin-guide/index
>> - The kernel build system <bailed/index>
>
> Where do the subdir names "bailed" above and "bugled" below come from?
No clue how that happened. Thanks for catching it, Randy.
>
>> - admin-guide/reporting-issues.rst
>> + Administration <admin-guide/index>
>> + Build system <bugled/index>
>
> ^^^^^^
>
>
> Thanks.
>
>> + Reporting issues <admin-guide/reporting-issues.rst>
>> User-space tools <tools/index>
>> - userspace-api/index
>> + User-space API <userspace-api/index>
>>
>> See also: the `Linux man pages <https://www.kernel.org/doc/man-pages/>`_,
>> which are kept separately from the kernel's own documentation.
>> @@ -89,8 +89,8 @@ platform firmwares.
>> .. toctree::
>> :maxdepth: 1
>>
>> - firmware-guide/index
>> - devicetree/index
>> + Firmware <firmware-guide/index>
>> + Firmware and Devicetree <devicetree/index>
>>
>>
>> Architecture-specific documentation
>> @@ -99,7 +99,7 @@ Architecture-specific documentation
>> .. toctree::
>> :maxdepth: 2
>>
>> - arch/index
>> + CPU Architectures <arch/index>
>>
>>
>> Other documentation
>> @@ -112,7 +112,7 @@ to ReStructured Text format, or are simply too old.
>> .. toctree::
>> :maxdepth: 1
>>
>> - staging/index
>> + Unsorted documentation <staging/index>
>>
>>
>> Translations
>> @@ -121,7 +121,7 @@ Translations
>> .. toctree::
>> :maxdepth: 2
>>
>> - translations/index
>> + Translations <translations/index>
>>
>> Indices and tables
>> ==================
>
Best,
Carlos
prev parent reply other threads:[~2023-12-11 1:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 1:19 [PATCH 0/1 " Carlos Bilbao
2023-12-11 1:20 ` [PATCH 1/1 " Carlos Bilbao
2023-12-11 1:41 ` Randy Dunlap
2023-12-11 1:58 ` Carlos Bilbao [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=77b25d0b-ceb4-4589-bf40-ff464e2a6b7f@vt.edu \
--to=bilbao@vt.edu \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rdunlap@infradead.org \
--cc=wedsonaf@gmail.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
all inboxes | Powered by JetHome®