Re: Why not have a Lilypond documentation set arranged as layman's Q: does LP do this?

[Pierre-Luc Gauthier]

Thanks Andrew for your input. I did write a few manuals (and still do)
for some system usage and I know how hard it can be to cover all what
a system can do and how to do it.

For the record, I learned a *lot* reading all (most) of the change logs :

http://lilypond.org/doc/v2.23/Documentation/changes/
http://lilypond.org/doc/v2.22/Documentation/changes/
http://lilypond.org/doc/v2.20/Documentation/changes/
http://lilypond.org/doc/v2.18/Documentation/changes/
http://lilypond.org/doc/v2.16/Documentation/changes/new-features-in-2_002e16-since-2_002e14
http://lilypond.org/doc/v2.14/Documentation/changes/

I also read "git log -p" on a daily basis.

Here are a few of my gotos might it help anyone :

https://lilypond.org/doc/v2.23/Documentation/internals/all-layout-objects.html
https://lilypond.org/doc/v2.23/Documentation/notation/lilypond-command-index
https://lilypond.org/doc/v2.23/Documentation/notation/chord-name-chart.en.html
https://lilypond.org/doc/v2.23/Documentation/notation/common-chord-modifiers.en.html
http://lilypond.org/doc/v2.23/Documentation/notation/percussion-notes.html
http://fritz.rmi.de/dokumentation/lilypond/Documentation/user/lilypond/Chords-mode.html#Chords-mode
https://lists.gnu.org/archive/html/lilypond-user/

FWIW
--
Pierre-Luc Gauthier