lilypond-devel
[Top][All Lists]
Advanced

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

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


From: Graham Percival
Subject: Re: Doc search: update to version 2.15, use it in the "site:" part (issue 5530043)
Date: Tue, 10 Jan 2012 06:09:11 +0000
User-agent: Mutt/1.5.20 (2009-06-14)

On Tue, Jan 10, 2012 at 12:15:43AM -0500, Pavel Roskin wrote:
> Quoting Graham Percival <address@hidden>:
> 
> >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



reply via email to

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