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 BD6A8DED3 for ; Wed, 31 Oct 2012 06:21:28 +0000 (UTC) Received: (qmail 70091 invoked by uid 500); 31 Oct 2012 06:21:28 -0000 Delivered-To: apmail-cayenne-dev-archive@cayenne.apache.org Received: (qmail 69927 invoked by uid 500); 31 Oct 2012 06:21:26 -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 69865 invoked by uid 99); 31 Oct 2012 06:21:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 06:21:24 +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; Wed, 31 Oct 2012 06:21:17 +0000 Received: (qmail 21401 invoked from network); 31 Oct 2012 06:24:07 -0000 Received: from unknown (HELO ?192.168.1.55?) (194.158.197.10) by vorsha.objectstyle.org with SMTP; 31 Oct 2012 06:24:07 -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: <50905443.2080509@maniatis.org> Date: Wed, 31 Oct 2012 09:20:55 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <507E393A.5020501@apache.org> <38AD87B8-DF9D-44D1-A983-25CCA8863AAC@objectstyle.org> <507E67EB.80804@gmail.com> <507E6AB7.2080301@maniatis.org> <507EB69D.3010505@maniatis.org> <535081D5-4704-4697-B283-B9B24BC253F9@objectstyle.org> <507F58A5.7090407@maniatis.org> <50809B87.8050200@maniatis.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> To: dev@cayenne.apache.org X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org I'll take a look at porting the news. Don't think we need to port many = past news.=20 > Why can't the third template extend skeleton?=20 My thinking was that we don't need left hand menu for the docs. For = instance looking at Docbook produced HTML I like how clean and = distraction free it is. Wanted to keep that across the board for docs. I = would imagine we'll just need a Cayenne header with a backlink to the = main site, and a copyright/privacy policy footer. Anyways, I'll refactor = the templates to maybe have a single skeleton and optional menu include. = Will need to play with it a bit. Andrus On Oct 31, 2012, at 1:27 AM, Aristedes Maniatis = wrote: > On 31/10/12 7:24am, Andrus Adamchik wrote: >=20 >> Note that second and third templates do not extend skeleton template, = as they are essentially incompatible. I just committed the changes, and = here are the rendered examples: >>=20 >> http://cayenne.staging.apache.org/download.html >> http://cayenne.staging.apache.org/doc30/api/index.html >> http://cayenne.staging.apache.org/doc30/overview.html >=20 > Why can't the third template extend skeleton? I tried to strip out the = bits of the html from the Confluence export which were incompatible, = leaving only (hopefully) compatible bits. Perhaps we can put back = skeleton and tweak the css a little to cope? >=20 > I think the next steps are just news and tying in the automated = docbook/javadoc builds for trunk documentation. >=20 > If we go down the Apache Blog approach for news, this is what we do: >=20 > {% for e in blog.list %} >

{{ e.title }}

>
{{ = e.content|safe|truncatewords_html:355 }}
>
> {% endfor %} >=20 > in our path.pm file: >=20 > [ qr!^/index\.mdtext$!, news_page =3D> { > blog =3D> ASF::Value::Blogs->new(blog =3D> "cayenne", = limit=3D> 4), > } ], >=20 >=20 > Pluses: >=20 > * people can add comments to the posts > * we get broader publicity on the main apache site as well with no = extra effort > * there is probably an rss feed >=20 > Minuses: >=20 > * I don't know if we can carry forward historical news, so we'd need = to handle that separately >=20 >=20 > Andrus, would you like to give this a try since you now have a local = environment? I can then style up the news items. Later on if we get = really clever it seems we might be able to have a feed on the side of = recent Jira comments and svn commits. That would be nice to show the = activity that happens behind the scenes. >=20 >=20 > Ari >=20 >=20 > --=20 > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >=20