Doc search: update to version 2.15, use it in the "site:" part

Doc search: update to version 2.15, use it in the "site:" part

site:lilypond.org/doc/v2.15 means that we want to look only under that
directory.  Leading plus doesn't force the exact search anymore.

[pkx166h, 2012-01-07 06:40:35]

Added Pavel as a CC in case there are any comments from anyone - then he can see
them

[Graham Percival, 2012-01-09 05:04:47]

I really don't like the hard-coded numbers, but I suppose I can't complain --
the patch doesn't make it any worse in that respect.

[Pavel Roskin, 2012-01-09 14:10:24]

I totally share your sentiment, but we depend on an external entity here, which
we cannot control.  Suppose we go from 2.15.x to 2.17.x and put the
documentation under "v2.17".  For some time, Google won't have the new location
in its index, so the search would get nothing.  It would be better to keep
"v2.15" in the search for a while and have a redirection from "v2.15" to
"v2.17".  Speaking of redirections, I would prefer that Lilypond had just two
versions of its documentation online - latest "stable" and latest "development".
 "v2.12" and "v2.14" shoould redirect to "stable", "v2.15" should redirect to
"development".  That would solve the issue with hardcoded version numbers and
keep Google happy.

[mail_philholmes.net, 2012-01-09 14:32:38]

----- Original Message ----- 
From: <plroskin@gmail.com>
To: <pkx166h@gmail.com>; <graham@percival-music.ca>
Cc: <reply@codereview-hr.appspotmail.com>; <lilypond-devel@gnu.org>
Sent: Monday, January 09, 2012 2:10 PM
Subject: Re: Doc search: update to version 2.15, use it in the "site:" 
part(issue 5530043)


>I totally share your sentiment, but we depend on an external entity
> here, which we cannot control.  Suppose we go from 2.15.x to 2.17.x and
> put the documentation under "v2.17".  For some time, Google won't have
> the new location in its index, so the search would get nothing.  It
> would be better to keep "v2.15" in the search for a while and have a
> redirection from "v2.15" to "v2.17".  Speaking of redirections, I would
> prefer that Lilypond had just two versions of its documentation online -
> latest "stable" and latest "development".  "v2.12" and "v2.14" shoould
> redirect to "stable", "v2.15" should redirect to "development".  That
> would solve the issue with hardcoded version numbers and keep Google
> happy.


+1

--
Phil Holmes

[Graham Percival, 2012-01-10 03:10:47]

On Mon, Jan 09, 2012 at 02:10:24PM +0000, plroskin@gmail.com wrote:
> I totally share your sentiment, but we depend on an external entity
> here, which we cannot control.  Suppose we go from 2.15.x to 2.17.x and
> put the documentation under "v2.17".  For some time, Google won't have
> the new location in its index, so the search would get nothing.  It
> would be better to keep "v2.15" in the search for a while and have a
> redirection from "v2.15" to "v2.17".  

Great point!  Could you add a comment to this effect to the top of
this file?  there's no way that I'll remember otherwise.

> Speaking of redirections, I would
> prefer that Lilypond had just two versions of its documentation online -
> latest "stable" and latest "development".  "v2.12" and "v2.14" shoould
> redirect to "stable", "v2.15" should redirect to "development".

We want to keep all stable docs available for historical reasons,
but I'm not opposed to directing people to
  /doc/stable/
  /doc/development/
rather than vX.Y.  If you feel like looking into this, the
htaccess is in Documentation/web/server/

- Graham

[proski_gnu.org, 2012-01-10 05:15:43]

Quoting Graham Percival <graham@percival-music.ca>:

> On Mon, Jan 09, 2012 at 02:10:24PM +0000, plroskin@gmail.com wrote:
>> I totally share your sentiment, but we depend on an external entity
>> here, which we cannot control.  Suppose we go from 2.15.x to 2.17.x and
>> put the documentation under "v2.17".  For some time, Google won't have
>> the new location in its index, so the search would get nothing.  It
>> would be better to keep "v2.15" in the search for a while and have a
>> redirection from "v2.15" to "v2.17".
>
> Great point!  Could you add a comment to this effect to the top of
> this file?  there's no way that I'll remember otherwise.

I believe the comment belongs to some other file that describes the  
release process.

If we keep things as is, the version change in the search would need  
to be done some time after the release.  I don't know how fast Google  
would index the new pages.

In the ideal case (which means changing the site layout), everything  
should be done at the time of the release and no "alarms" should be  
needed for additional changes.

>> Speaking of redirections, I would
>> prefer that Lilypond had just two versions of its documentation online -
>> latest "stable" and latest "development".  "v2.12" and "v2.14" shoould
>> redirect to "stable", "v2.15" should redirect to "development".
>
> We want to keep all stable docs available for historical reasons,
> but I'm not opposed to directing people to
>   /doc/stable/
>   /doc/development/
> rather than vX.Y.  If you feel like looking into this, the
> htaccess is in Documentation/web/server/

When searching for Lilypond related topics on Google, I constantly get  
directed to v2.12 unless I add "v2.15" to the search line.  But I  
often want to find information both on the Lilypond site and  
elsewhere, so adding "v2.15" would lose the external links.

I'm not against hosting historic documentation, but it would be nice  
to "deemphasize" is somehow.

-- 
Regards,
Pavel Roskin

[Graham Percival, 2012-01-10 06:08:46]

On Tue, Jan 10, 2012 at 12:15:43AM -0500, Pavel Roskin wrote:
> Quoting Graham Percival <graham@percival-music.ca>:
> 
> >Great point!  Could you add a comment to this effect to the top of
> >this file?  there's no way that I'll remember otherwise.
> 
> I believe the comment belongs to some other file that describes the
> release process.

We won't look at it.  Trust me, we're just not that organized.  A
comment at the top of the search.ithml file is much less likely to
be ignored.

> >We want to keep all stable docs available for historical reasons,
> >but I'm not opposed to directing people to
> >  /doc/stable/
> >  /doc/development/
> >rather than vX.Y.  If you feel like looking into this, the
> >htaccess is in Documentation/web/server/
> 
> When searching for Lilypond related topics on Google, I constantly
> get directed to v2.12 unless I add "v2.15" to the search line.  But
> I often want to find information both on the Lilypond site and
> elsewhere, so adding "v2.15" would lose the external links.
> 
> I'm not against hosting historic documentation, but it would be nice
> to "deemphasize" is somehow.

Yes, and using the /doc/stable/ vs. /doc/devel/ links would surely
de-emphasize it.  We could even tell google to ignore the old doc
pages, although I'm not certain we want it removed from the cache
entirely... but given their pagerank algorithm, if we didn't have
so many links to the explicit /doc/vX.Y/ pages, those pages would
be de-emphasized already.

Cheers,
- Graham

[pkx166h, 2012-01-13 11:57:37]

Pavel,

This patch has been approved and pushed.

committer	James Lowe <pkx166h@gmail.com>	
Fri, 13 Jan 2012 11:54:08 +0000 (11:54 +0000)
commit	427bb2b004227f3afc7de10dfd896fc375cbc320

Please can you close this Rietveld issue?

Thank you for your patch.

James

[Pavel Roskin, 2012-01-13 16:56:54]

I don't think I can close this.  I see gray "Can't Edit" over "Publish+Mail
Comments".  I tried adding my gnu.org address as an alias in gmail but it
changed nothing.  Sorry for not being able to participate more in the
discussion!

[Graham Percival, 2012-01-13 16:59:47]

On 2012/01/13 16:56:54, Pavel Roskin wrote:
> I don't think I can close this.

That is quite correct -- James Lowe owns this issue, so only he can close it.

[pkx166h, 2012-01-14 00:56:24]

On 2012/01/13 16:59:47, Graham Percival wrote:
> On 2012/01/13 16:56:54, Pavel Roskin wrote:
> > I don't think I can close this.
> 
> That is quite correct -- James Lowe owns this issue, so only he can close it.

Sorry, I didn't realise I had the Rietveld as well.

Closed.