This document describes our site setup: what is where and how does it work.
Overview
Our website and documentation are kept in Confluence.
Since the confluence instance at https://cwiki.apache.org/confluence/
isn't capable of handling a lot of incoming requests, all spaces are statically exported.
The Autoexport plugin for Confluence is responsible for that. Once a page in Confluence changes, that page gets re-exported automatically. The Autoexport plugin is configured to export the pages to a directory on thor (the machine Confluence is running on). From there a cron job copies the exports to /www/confluence-exports on people.apache.org.
On people.apache.org another cron job copies the exported Tapestry space to ~uli/public_html/tapestry-site/ which is available as http://people.apache.org/~uli/tapestry-site/.
This will shortly be updated to copy our space to a /www/tapestry.apache.org which is the folder that itself is copied out and available as http://tapestry.apache.org.
Yes, this is a bit Rube Goldberg, and the multiple steps, hops, and cron jobs mean it can be quite some time between a change in Confluence, and the content being visible (possibly a couple of hours).
Content copied to /www/tapestry.apache.org is not immediately visible; yet another cron job (!) copies this content to the main Apache web server, about once an hour. On the other hand, content ~uli is available in real time.
Website structure
The Index page includes the Banner and Key Features pages as well as the blog posts. All other pages are just plain pages and may or may not include other parts. In addition the Navigation, Small Banner and Footer pages exist.
Our Autoexport template glues everything together. It adds the contents of the Navigation and Footer pages in the appropriate places and on all pages except the Index page. It also adds the contents of the Small Banner page as well as the breadcrumbs navigation.
Because we include some pages in others it is sometimes necessary to reexport the whole space because the Autoexport plugin will only export the changed page, not the pages where the changed page is included. To do so you have to be a confluence administrator. You can then manually export our space via the Autoexport administrative console.
HLS: I've noticed that pages with footnotes that are combined with the {include} macro do not render correctly ... the footnote numbers and anchors reset back to 1 for each included page. Perhaps there's a way to fix that with the template?
Updating the template
You must be a Confluence Administrator.
Unfortunately, Confluence can't read content directly from Subversion.
Checkout a workspace to https://svn.apache.org/repos/asf/tapestry/tapestry-site/branches/post-5.2-site
Edit the autoexport_template.txt there, then check it back in.
From the Browse menu (at the top of the Confluence page), select Confluence Admin.
From the Configuration left side menu, click Auto Export.
From AutoExport Templates Management you can scroll down to Apache Tapestry and click Edit Template.
Copy the contents of the autoexport_template.txt file to the text area and hit update.
Now, under Rebuild exported spaces, select Apache Tapestry and click Export Space(s).