Re: Retiring app menus - planning for 3.32.0

Bastien Nocera <hadess hadess net> wrote:
Putting aside the issue of outdated user docs,

Well, it's a pretty big factor here.

Can't we just remove out of date user docs?

I realise that my line of reasoning is somewhat hypothetical here, but
if there are issues with the user docs, we ought to fix them.

 do you experience any
advantages having keyboard shortcuts in the shortcuts window, as
opposed to the help?

It's faster to access for users, has terser explanations (no need to
create sentences to describe actions) and

To be clear, I'm still thinking this through but, if you had a page in
the user docs which was a simple table of keyboard shortcuts, which
was one click away in the user docs, there wouldn't be all that much
to separate it from the keyboard shortcuts windows. And the advantage
would be more integrated user documentation (I think that's
essentially what the keyboard shortcut windows are). This would reduce
the number of menu items, allows cross-linking, and so on.

it's usually better updated
as it lives in the code, as opposed to being separate in the docs.

I can see how that's an advantage, but it also feels like a bit of a
workaround, if we assume that we need up-to-date user docs one way or


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]