Return-Path: X-Original-To: apmail-cayenne-dev-archive@www.apache.org Delivered-To: apmail-cayenne-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CD429B72 for ; Thu, 8 Nov 2012 08:29:22 +0000 (UTC) Received: (qmail 11050 invoked by uid 500); 8 Nov 2012 08:29:22 -0000 Delivered-To: apmail-cayenne-dev-archive@cayenne.apache.org Received: (qmail 10955 invoked by uid 500); 8 Nov 2012 08:29:21 -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 10925 invoked by uid 99); 8 Nov 2012 08:29:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 08:29:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.78.103.231] (HELO vorsha.objectstyle.org) (208.78.103.231) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 08 Nov 2012 08:29:14 +0000 Received: (qmail 19768 invoked from network); 8 Nov 2012 08:32:21 -0000 Received: from unknown (HELO ?192.168.1.22?) (194.158.197.10) by vorsha.objectstyle.org with SMTP; 8 Nov 2012 08:32:21 -0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Website CMS From: Andrus Adamchik In-Reply-To: Date: Thu, 8 Nov 2012 11:28:51 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <4E6684E7-24F8-4145-AADB-B6B77D8C85B5@objectstyle.org> References: <507E393A.5020501@apache.org> <508DDAFD.2040204@maniatis.org> <508E3811.7040300@maniatis.org> <836D2ABB-560B-4BE2-A196-785AA4C8BB6E@objectstyle.org> <508F924A.1030908@maniatis.org> <0C4C98E1-0F02-425A-9DB8-A88C36AED257@objectstyle.org> <508FA4BD.50408@maniatis.org> <7CFA3553-4A5E-4B26-91C0-0A35F147AADD@objectstyle.org> <50905443.2080509@maniatis.org> <5090D3B8.5050102@maniatis.org> <40CD90D7-15B7-4D41-BDE3-43CF2FCB3F98@objectstyle.org> <50965 873.4070806@maniatis.org> <88C07F0F-7C53-4BA4-8909-06F1223BF6AC@objectstyle.org> <5096F6E1.4040004@maniatis.org> <50977802.6010802@maniatis.org> <2AA5D963-8FA7-4EAB-AF27-766643A16081@objectstyle.org> <333FE7E6-5F9B-45B4-B2F9-EE69CF1C6C4A@objectstyle.org> <509AF9 62.2020401@maniatis.org> To: dev@cayenne.apache.org X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org Looks like we still need one more redirect though. 3.0 docs were served = as /doc till now, so this has to go to /doc30=85 Hmm=85 I might change = the new /doc/ to /docs/ then to avoid redirect confusion. BTW the site seems to be in process of publishing now: = http://cayenne.apache.org/ hopefully will be up shortly. Andrus On Nov 8, 2012, at 10:56 AM, Andrus Adamchik = wrote: > On Nov 8, 2012, at 3:14 AM, Aristedes Maniatis = wrote: >>> Today loaded 3.1 javadocs and docbook HTML to the cms site. We have = a total of 4 independent books in 3.1 (will probably refactor the whole = docbook structure soon to make them easier to manipulate). Manually = copying the folders wasn't too bad. The worst part was "git svn dcommit" = after a Javadocs dump. But never the less it worked. >>>=20 >>> Notice the new docs structure. I wanted the subfolders to logically = follow dropdown menus, so instead of calling it /doc31/, I went with = /doc/3_1/ : >>>=20 >>> http://cayenne.staging.apache.org/doc/3_1/index.html >>=20 >> Not sure how changing the path syntax helps. If you really want to do = that we'll need redirects from all the old simpler URLs to the new = structure. >> Remember that people will end up in doc pages from a google search = and may just change the URL to go to a different version. >=20 > I didn't touch 1.2, 2.0, 3.0 layout. So no need for redirects. I = strongly support the notion that we shouldn't be changing the existing = well-publicized URLs without a cause. And if we do, always provide a 301 = redirect (see "content/.htaccess"). But this is not the case here.=20 >=20 > The new scheme starts with 3.1 release. Among other things the new CMS = freed us from the directory and file naming imposed by Confluence = Autoexport, so I figured the URLs might follow the menu hierarchy for = the docs. Also "unflattening" the top directory structure seems like a = good thing for our own sanity. >=20 >> I also suggest a redirect >>=20 >> /doc/latest/ --> /doc/3.1/ >>=20 >> That makes it easier to refer people to the docs and for the links in = mailing list archives to remain pointing to the current docs. >=20 > I've been thinking about this for some time. A "latest" symlink is = both good and bad. The positive is that it creates a perception of a = single set of docs. The negative is that we do have multiple versions of = the docs after all and it is not always clear what "latest" means on any = given day and associating "latest" with this moving target is not always = such a clear cut. As Cayenne accumulates more major releases, I feel = like using explicit versioning everywhere will save us and users from = more trouble. >=20 > Taking your example, links in mailing list archives would actually = work better with no "latest" symlink. Consider that some docs go away = occasionally (e.g. dataviews are no longer in Cayenne, jpa, etc.). So = this example seems to validate the version-aware URL approach. >=20 >>> Ari, any word on publishing our staging to the live site? >>=20 >> Yes, spoke to infra and created a ticket a few days ago. It is on = their list. >=20 > Awesome. >=20 > Andrus >=20