[Top][All Lists]

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

Re: `Help Us' section duplicated

From: Simon Albrecht
Subject: Re: `Help Us' section duplicated
Date: Thu, 23 Jul 2015 18:01:35 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Hi Mark,

it took me a while to extract the exact point from your long text; but now I may summarize: <http://lilypond.org/doc/v2.19/Documentation/web/help-us> and <http://lilypond.org/doc/v2.19/Documentation/contributor/help-us> contain the same text.

Am 23.07.2015 um 01:02 schrieb markdblackwell:
This, combined with referring the reader (as it turns out) to the same
content, yet in another manual, might somewhat confuse readers as to why.
(It did so, for me.)

Also, some readers might be motivated to check whether or not the content
indeed is exactly duplicated (since we don't say so).
Both these questions are unlikely to be relevant to a vast majority of the readers, I think. Probably no one except from you has been irritated by this. – The duplicated text passages are referenced from a common source. They have not, of course, been copied manually – that would be absurd given the sophistication and professionality involved in all of the setup and design, and the general efforts to avoid code duplication. – They have certainly been duplicated by design, and I agree that it makes sense, since the information is needed both on the ‘surface’ of the website and as the beginning of a comprehensive discussion in the CG.
  Question: The first page of the Contributor's Guide, for people who are
considering helping LilyPond, includes a link to `Help us'. Should that link
go to section `Help us' of:

1. The Contributor's Guide manual?; or of

2. The Web/General Information manual?
Of course, this only links the subsection within the CG, as with all other links of the kind. There’s no reason to change that.

I hope this clarifies the matter.
Thanks for making so detailed thoughts on this.

Yours, Simon

reply via email to

[Prev in Thread] Current Thread [Next in Thread]