Robert Hickman <robehick...@gmail.com> writes: > On 25 April 2018 at 18:44, Karlin High <karlinh...@gmail.com> wrote: >> On 4/25/2018 12:38 PM, Kieren MacMillan wrote: >>> >>> Hi Robert, >>> >>>> Many pages duplicate content or say 'please read page xyz first' >>>> because I recognise that people will enter the site from any page >>>> and I cannot make any assumptions about what they already know. >>> >>> >>> This is a great suggestion. Perhaps you can contribute such links as you >>> continue your Lilypond journey — no doubt there are lots of places these >>> redirects would be helpful to users (new and experienced). >> >> Like Kieren said, contributions welcome. >> >> There are some policies of not having documentation repeat things, though. >> >> <http://lilypond.org/doc/v2.19/Documentation/contributor/introduction-to-documentation-work> >> > > IMO, if it makes the documentation hard to use those policies should > be thrown out or tamed. Terseness is valuable but not at the expense > of making something difficult to use.
The Learning Manual can be worked through in something like three sessions, one skimming, and two more thorough after one has a hang of it. The Notation Reference is less of a linear exercise. It already contains something 800+ pages or so. That in itself is making things difficult to use. However, links (and/or printed references) don't take a lot of additional space. The current documentation is the work of ten thousands of hours from various contributors. It's easy to wave your hands and say "not good, I want you all to redo it better" but that will not result in changes getting done, not least of all since many of the contributors are no longer around seeing you wave your hands. It's nice talking in the passive voice like "those policies should be thrown out or tamed", but the work does not magically do itself. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
