All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: David Gow <davidgow@google.com>,
	Sadiya Kazi <sadiyakazi@google.com>,
	linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH RFC V2] docs: Add more information to the HTML sidebar
Date: Sat, 04 Feb 2023 14:39:27 -0700	[thread overview]
Message-ID: <87357lrtyo.fsf@meer.lwn.net> (raw)
In-Reply-To: <cb0d683b-8abd-ecb1-389d-c45550e7bbf3@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

>> But I see a major problem on small/narrow screens.
>> The sidebar is now kept at the top, and by clicking/tapping a link in the
>> TOC, I can't jump to the section I want to see.
>> 
>> Sorry, but this is not usable at all.
>
> To be clear, I meant "on small/narrow screens".
> On normal PC screens, this resolves the issues I mentioned earlier.
>
> So I'm OK with this goes into v6.3. Maybe add a note on small screen
> devices in the Changelog.

I see what you're saying.

The best solution to this, I guess, would be to hide the contents menu
behind an icon in the small-screen view.  Doable, I'll try to find some
time to make that happen.

> BTW, I very much like the way LWN's site navigation behaves on small
> screen devices. LWN is designed to be accessible without hierarchical
> structure of documents, which is the opposite of how kernel documentation
> is managed based on the nested TOC entries.

Yeah, but for the kernel documentation the hierarchy is the only
structure we have.  Making less of a mess out of it has been a many-year
project, got a long way to go...

Thanks,

jon

  reply	other threads:[~2023-02-04 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 23:09 [PATCH RFC V2] docs: Add more information to the HTML sidebar Jonathan Corbet
2023-02-04  0:02 ` Jonathan Corbet
2023-02-04  0:20   ` Akira Yokosawa
2023-02-04  7:33     ` Akira Yokosawa
2023-02-04 21:39       ` Jonathan Corbet [this message]
2023-02-04  0:02 ` Randy Dunlap
2023-02-06 19:25   ` Jonathan Corbet
2023-02-14 18:25     ` Randy Dunlap
2023-02-14 18:33       ` Jonathan Corbet
2023-02-15 10:23         ` Akira Yokosawa
2023-02-16 23:55           ` Jonathan Corbet
2023-02-04  4:36 ` David Gow
2023-02-06 11:22 ` Sadiya Kazi

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=87357lrtyo.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=davidgow@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=sadiyakazi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.