The Incubator website is generated by the Apache CMS, but it
is still using the Anakia-based page generation mechanism that was
triggered by a CMS external build script.
This means that you can edit the content either directly in svn
(and use ant to generate and check the results), or edit via the
CMS interface, but final publishing has to be done via the CMS
(see below for how).
The source to the Incubator website lives at:
The incubator website is built using CMS. After changes are made,
you must publish the website.
People with commit access to the "incubator" SVN can edit the source
documents in the "content" directory. That is any ASF Member and
any committer on a current podling in incubation. So you can all help to
keep your project's Status page up-to-date, and if you find problems with
the "guidelines" docs then can immediately fix them.
If unsure, then discuss changes on the general mailing list.
Note that the "policy" documents need special treatment.
Anyone else can send patches to those documents to the INCUBATOR issue tracker.
Checkout the Incubator SVN site
svn co https://svn.apache.org/repos/asf/incubator/public/trunk incubator
Edit the source documents
The source content is in Anakia xdoc format at the "content" directory.
Add a new document
Add new documents in the content directories, then do 'svn add'.
Please generate the website yourself and check in the changes.
If you have any problems, ask for help on the Incubator's
In the top-level "incubator" SVN directory, do 'ant'
to render the HTML files into the
You should review those changes before committing.
(If you don't have ant installed, you can run build.sh or build.bat
instead.) If the site built without errors, then do the usual
SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'.
Review your changes via the
mailing list. This list will also have buildbot output from running
staging builds of the website. If you want to view your changes, you can go to
To update the website, visit Publish site
and fill out the form. Don't forget to give the CMS build system time to build your changes!
The CMS provides a page for following the build process.
Make sure that your subversion client is properly
See other notes for maintenance of
apache.org project websites.
If you are still having trouble committing, then perhaps the Subversion
authorization is not yet properly
to enable your group's access.