Return-Path: Delivered-To: apmail-cayenne-dev-archive@www.apache.org Received: (qmail 62102 invoked from network); 17 Feb 2010 08:54:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2010 08:54:12 -0000 Received: (qmail 83272 invoked by uid 500); 17 Feb 2010 08:54:12 -0000 Delivered-To: apmail-cayenne-dev-archive@cayenne.apache.org Received: (qmail 83230 invoked by uid 500); 17 Feb 2010 08:54:12 -0000 Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cayenne.apache.org Delivered-To: mailing list dev@cayenne.apache.org Received: (qmail 83220 invoked by uid 99); 17 Feb 2010 08:54:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 08:54:12 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [59.167.240.32] (HELO fish.ish.com.au) (59.167.240.32) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 08:54:02 +0000 Received: from ip-149.ish.com.au ([203.29.62.149]:56383) by fish.ish.com.au with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1Nhg1q-0004JU-1s for dev@cayenne.apache.org; Wed, 17 Feb 2010 20:17:06 +1100 Message-ID: <4B7BAE8F.7070205@maniatis.org> Date: Wed, 17 Feb 2010 19:53:35 +1100 From: Aristedes Maniatis User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: dev@cayenne.apache.org Subject: Re: wiki pages design References: <6C86227C-4602-4E2E-898B-F3BAF8A00EBA@objectstyle.org> <4B772D6B.4080608@maniatis.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 17/02/10 7:48 PM, Andrus Adamchik wrote: > On a related note, we need some visual separation of the docs for > different versions on the site. I've seen more than one case when users > go confused, e.g. when Google returns an old version of the docs for a > given search term. I guess after 3.0 goes final, we can remove 1.2/2.0 > docs from the site completely, and refer people to Cayenne downloads for > the old docs, and then style 3.1 and 3.0 docs differently. > > (Also as I mentioned before, multiple versions of the docs reduce our > google ranking for a given search term, but that's a separate story). We could publish robots.txt to keep Google out of everything but the current docs... Ari -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A