Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cocoon Wiki" for change notification.
The following page has been changed by DavidCrossley: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate ------------------------------------------------------------------------------ * CocoonReleaseHowTo = WHERE DOES THE WEBSITE CONTENT COME FROM? = - The website content comes from the http://svn.apache.org/repos/asf/cocoon/site/ repository. + The website content comes from the http://svn.apache.org/repos/asf/cocoon/site/ repository. These are the generated documents. - The src subdirectory contains the content that we write (in xdoc format), and the corresponding website pages (generated by Forrest) are committed to the site subdirectory, to make it easy to update or restore the content on the live web server. This means that any manual changes to pages in the site subdirectory are ''lost'' when the site is regenerated using Forrest. + The source for the top-level website is in the src subdirectory containing the content that we write (in xdoc format), and the corresponding website pages (generated by Forrest) are committed to the site subdirectory, 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 the top-level http://cocoon.apache.org/ index page, for example, is found at http://svn.apache.org/repos/asf/cocoon/site/src/documentation/content/xdocs/index.xml + The source of http://cocoon.apache.org/ index page, for example, is found at http://svn.apache.org/repos/asf/cocoon/site/src/documentation/content/xdocs/index.xml = HOW ABOUT DAISY? = - Since 2.1.8, the documentation (apart from the general website pages) is written using daisy at http://cocoon.zones.apache.org/, and Daisy-generated pages are processed by Forrest (using forrest trunk) to generate the static pages at http://cocoon.apache.org/2.1/ (still in experimental phase). + Since 2.1.8, the documentation (apart from the general website pages) is written using daisy at http://cocoon.zones.apache.org/, and Daisy-generated pages are processed by Forrest (using forrest trunk) to generate the static pages (still in experimental phase). + Get these two repositories: + * svn co https://svn.apache.org/repos/asf/cocoon/whiteboard/daisy-to-docs cocoon-daisy-to-docs + * svn co https://svn.apache.org/repos/asf/forrest/trunk forrest-trunk + - People are still working out the details of this process, we should document it here when it's stabilized. For the meantime, see below for how to produce the documentation. + People are still working out the details of this process, we should document it here when it's stabilized. For the meantime, see the old notes below for how to produce the /2.1/ documentation. = HOW TO UPDATE AN APACHE COCOON WEBSITE = @@ -37, +41 @@ == B) Checkout Cocoon Site SVN == - Checkout SVN url https://svn.apache.org/repos/asf/cocoon/site/ into site. 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. + Checkout SVN url https://svn.apache.org/repos/asf/cocoon/site/ into cocoon-site. 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) @@ -65, +69 @@ == D) Upload site into SVN == - Ensure that your cocoon-site is up-to-date (svn update). Copy the generated files to the relevant directory under cocoon-site/site/ and then remove removed files, add added files, svn propset, etc. Then commit results into cocoon-site. + Ensure that your cocoon-site is up-to-date (svn update). 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' to commit the results into cocoon-site. == E) Update site on the server ==
