cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aristedes Maniatis <>
Subject Re: Website CMS
Date Tue, 30 Oct 2012 22:27:15 GMT
On 31/10/12 7:24am, Andrus Adamchik wrote:

> 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:

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?

I think the next steps are just news and tying in the automated docbook/javadoc builds for
trunk documentation.

If we go down the Apache Blog approach for news, this is what we do:

{% for e in blog.list %}
       <h2><a href="{{ e.url }}">{{ e.title }}</a></h2>
       <div class="section-content">{{ e.content|safe|truncatewords_html:355 }}</div>
     {% endfor %}

in our file:

[ qr!^/index\.mdtext$!, news_page => {
          blog     => ASF::Value::Blogs->new(blog => "cayenne", limit=> 4),
} ],


* 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


* I don't know if we can carry forward historical news, so we'd need to handle that separately

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.


Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

View raw message