This info is for Cocoon committers who need to update Cocoon's 2.1 website.

FIXME: Some out-of-date content

See this dev discussion about the issue of the Daisy on the Cocoon zone server being down, and so Forrest cannot generate the docs. Date: 17 Jan 2012 Subject: resurrect the Cocoon documentation

Some of the content below is still relevant.

See also


Get the docs that are generated daily from Daisy by Forrestbot. Commit these docs to the SVN which holds the Cocoon website. Here is how ...

That is it. There is a cronjob on the server to do 'svn update'.

See below for further information.

Verifying The Generated Site

The above site package is generated by Forrest every 12 hours. You only need to update the site manually (see below) if you don't want to wait for the next automated update.

You can preview what is in the download by looking at the Forrest Zone

You can also verify that there are no broken links by looking at the broken links xml file (it should be empty of course).


The website content is held in the repository.

All generated documents are held in the "site" sub-directory.

The source for the top-level website is in the "src" sub-directory containing the content that we write (in xdoc format), and the corresponding website pages (generated by Forrest) are committed to the "site" sub-directory, to make it easy to update or restore the content on the live web server. This means that any manual changes to html pages in the site subdirectory are lost when the site is regenerated using Forrest.

The source of index page, for example, is found at


Since 2.1.8, the documentation (apart from the top-level website pages described above) is written using Daisy at and Daisy-generated pages are processed by Forrest (using forrest trunk) to generate the static pages (still in experimental phase).

If you want to build the site locally, then get these two repositories and follow the detailed instructions below.


See the overview above. Committers should let forrestbot do the work, and use the "quick update" method of committing the final docs to cocoon/site SVN.

Here are the details ...

Forrest notes

For review purposes the Forrestbot generates the 2.1 docs every day. See Forrest zone. However, publishing the website is still a manual process done occasionally by committers.

Process notes for Cocoon Release day

General notes

A) Checkout the cocoon-site SVN

If you have checkout already, just update it. This repository holds the generated docs for both the top-level website and for each set of version-specific docs. It also holds the source xdocs and the Forrest config files for the top-level website.

NOTE: cocoon-site is more than 60 Mb. You can checkout only part of it, say, for Cocoon 2.1, cocoon-site/site/2.1 (35Mb)

NOTE: The javadocs are not stored in the cocoon-site SVN. They can easily be regenerated. Use scp to copy them to the website.

B) Generate top-level site

For the top-level website, just do the command 'forrest' in the top-level cocoon-site directory. After generation is complete, the site will be ready at the build/site/ directory. Use forrest-trunk.

View the generated docs to be sure that everything is as you would expect.

Now copy the generated docs:

Note: There is a glitch, probably because the 2.1 site has changed its presentation and the top-level site config is not in sync. So only copy the *.html *.pdf

C) Generate the 2.1 docs

Note: That is taking too much time locally (over a minute per doc). A good solution is to copy the tar file of generated docs from the forrest zone (see above) to your local machine. Look our for line-endings if you are not on unix.

D) Upload site into SVN

Ensure that your cocoon-site is up-to-date (do 'svn update' again). Copy the generated files to the relevant directory under cocoon-site/site/ and then do the usual SVN stuff: 'svn status' 'svn add' 'svn diff' 'svn commit'

E) Update site on the server

Steps are:


Other notes:

CocoonWebsiteUpdate (last edited 2013-03-06 12:17:12 by 123-51-22-91)