From: Dimitri Fontaine <dfontaine@hi-media.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Craig James <craig_james@emolecules.com>, pgsql-performance@postgresql.org
Subject: Re: Using more tha one index per table
Organization: Hi-Media
References: <4C46A23B.2090606@acteos.com> <4C470B69.6080304@2ndquadrant.com>
	<4C47953D.9090603@postnewspapers.com.au>
	<4C4798D5.7030700@emolecules.com> <4C47A341.7010905@2ndquadrant.com>
User-Mail-Address: dfontaine@hi-media.com
Date: Sun, 25 Jul 2010 10:29:26 +0200
In-Reply-To: <4C47A341.7010905@2ndquadrant.com> (Greg Smith's message of "Wed,
	21 Jul 2010 21:47:45 -0400")
Message-ID: <m24ofonevt.fsf@hi-media.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (darwin)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Greg Smith <greg@2ndquadrant.com> writes:
> Craig James wrote:
>> By using "current" and encouraging people to link to that, we could
>> quickly change the Google pagerank so that a search for Postgres would
>> turn up the most-recent version of documentation.
>
> How do you propose to encourage people to do that?  

What about adding version information in huge letters in the top blue
bar, with all versions available in lower letters than what you're
looking at, and with current version nicely highlighted (color,
underlining, subtitle, whatever, we'd have to find a visual hints).

In other words, make it so big that you don't have to read the page
content to realise what version it is you're looking at.  Maybe we would
need to have this information stay visible on the page at the same place
when you scroll, too.

Regards,
-- 
dim