Re: Web site manual search defaulting to 2.17

[Federico Bruni]

2014/1/23 Phil Holmes <address@hidden>

> "Federico Bruni" <address@hidden> wrote in message
> news:address@hidden
>
>  2014/1/23 Nick Payne <address@hidden>
>>
>>  Using the search box at top right on the LP web site is searching the
>>> 2.17
>>> rather than the 2.18 manuals. e.g. The search submitted to google is:
>>>
>>> https://www.google.com/search?btnG=Google+Search&brute_
>>> query=bar+engraver&q=site%3Alilypond.org%2Fdoc%2Fv2.17+bar+engraver
>>>
>>> Shouldn't the default search be the current stable version?
>>>
>>>
>> There's an issue already:
>> https://code.google.com/p/lilypond/issues/detail?id=2909
>>
>> I think that it's just a matter of waiting for google to reindex the
>> pages.
>> You can try and see that a search on v2.17 gives more results than v2.18
>> But I agree that the version should be the stable. I can't remember why
>> the
>> dev version is set
>>
>
> As it stands, the search box will only search one set of documents.  I
> believe we use the development set, since that will progressively improve
> as people fix documentation bugs.
>
> An alternative might be to think of some JavaScript that picks up the
> version number from the URL of the documentation page and uses this as the
> search site?
>
>
Just to clarify: the problem is just in the "general search", the one you
see in the home page and all the pages of the website, where there's no
version number in the URL.
The search in each stable version of the documentation can be easily fixed,
because each version is "frozen" in a separate branch. Now we can update
search-box.ihtml in 2.18 branch without affecting the current version.

It's a trade-off:
If we keep 2.18 in the current version, the search in 2.19 manuals will
look up 2.18 pages.
If we put 2.19, a user might search the development version instead of the
stable.  I think that the user should learn and use the search bar within a
manual.


> A check with Google shows it seems to have indexed both 2.18 and 2.19 so
> the search box could be updated now.


yes, I've added a comment here:
https://code.google.com/p/lilypond/issues/detail?id=2909#c5