public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 0/4] Rewrite the top-level index.rst
Date: Fri, 23 Sep 2022 07:45:30 -0600	[thread overview]
Message-ID: <875yhep5l1.fsf@meer.lwn.net> (raw)
In-Reply-To: <7f02143c-461f-268b-0f17-7fe20a7423d6@leemhuis.info>

Thorsten Leemhuis <linux@leemhuis.info> writes:

> On 22.09.22 22:41, Jonathan Corbet wrote:
>> The top-level index.rst file is the entry point for the kernel's
>> documentation, especially for readers of the HTML output.  It is currently
>> a mess containing everything we thought to throw in there.  Firefox says it
>> would require 26 pages of paper to print it.  That is not a user-friendly
>> introduction.
>
> That's true, but is it maybe good or even important for googleability?
> When you talked about this in your LPC talk this went on in the matrix chat:
>
> ```
> Nur Hussein
> I feel like every existing page needs to be accessible (somehow)
> from that starting page
>
> Zsuzsa Nagy
>
> access to all pages <- findability from a search engine (technical
> author talking here)
>
> step #2 in-site search for those who already landed on your pages
> ```

So every page remains accessible, just like they are now.  They just
aren't linked directly from the front page - as many pages already are
not.  I honestly don't understand what the problem is here.

*No* site links everything directly on its front page.  Even if it had
an effect on search engines, I think it would be wrong to prioritize SEO
over basic usability.

>> This series aims to improve our documentation entry point with a focus on
>> rewriting index.rst.  The result is, IMO, simpler and more approachable.
>> For anybody who wants to see the rendered results without building the
>> docs, have a look at:
>> 
>>   https://static.lwn.net/kerneldoc/
>
> I still think we're doing all this to build something for users and
> hence docs for users should be at the top spot. I'd even think "those
> people are selfish" if I'd look into the docs of a software and find
> texts for developers at the top spot.

Again ... who are the users?  I maintain that the actual users of our
docs are primarily kernel developers.

>> Unless I get screams I plan to slip this into 6.1.  It is definitely not
>> the final form of the front page, but I doubt we'll ever get there; we can
>> change it in whatever ways make sense.
>
> My 2 cent: why the rush? I'd say: let's try to get some feedback from
> Zsuzsa and experts on docs first. I'd be willing to approach them. If
> that doesn't work out over the next few weeks, just merge what you have
> for 6.2.

I want to do it because it's a clear step forward and has already been
pending for a month.  It is surely not perfect, and there will
undoubtedly be changes, perhaps big ones, to come, but I cannot imagine
a scenario where we want to go back to the mess we have now.

Thanks,

jon

  reply	other threads:[~2022-09-23 13:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 20:41 [PATCH v2 0/4] Rewrite the top-level index.rst Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 1/7] docs: promote the title of process/index.html Jonathan Corbet
2022-09-23 17:53   ` David Vernet
2022-09-23 18:31     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-23 19:02   ` Randy Dunlap
2022-09-23 19:07     ` Jonathan Corbet
2022-09-24  2:05   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-24  2:13   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-24  2:14   ` David Vernet
2022-09-22 20:41 ` [PATCH v2 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-23  7:45   ` Bagas Sanjaya
2022-09-24  2:10   ` kernel test robot
2022-09-24  2:20   ` David Vernet
2022-09-25  3:54   ` Bagas Sanjaya
2022-09-25 21:29     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 6/7] docs: Expand the front-page CPU-architecture section Jonathan Corbet
2022-09-24  2:25   ` David Vernet
2022-09-25 21:50     ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-23  4:25   ` Bagas Sanjaya
2022-09-23 13:39     ` Jonathan Corbet
2022-09-25  3:18       ` Bagas Sanjaya
2022-09-25  3:48         ` Randy Dunlap
2022-09-25  3:52           ` Bagas Sanjaya
2022-09-23 18:44   ` Randy Dunlap
2022-09-23 19:06     ` Jonathan Corbet
2022-09-23  8:09 ` [PATCH v2 0/4] Rewrite the top-level index.rst Jani Nikula
2022-09-23  8:55 ` Thorsten Leemhuis
2022-09-23 13:45   ` Jonathan Corbet [this message]
2022-09-23 14:43     ` Thorsten Leemhuis
2022-09-23 15:03       ` Jonathan Corbet
2022-09-23 17:45         ` Kees Cook
2022-09-24  1:56         ` David Vernet
2022-09-23 18:48     ` Randy Dunlap

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=875yhep5l1.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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