The complete separation between content and style leads to a very powerful multi-channeling solution where you can apply different stylesheets to the same content and generate different flavors of it. A couple of existing web sites have been xml-ized to show you how easier it is to handle pure-content markup. An example of more complex use of XSLT for navigation and content filtering. Since XML is based on Unicode, it can be used to encode all types of languages. Here is an example of the power of such an approach with the help of those i18n and l10n Cocoon facilities. Separation of content and style allows not only to serve your content in different ways, but also to syndicate, aggregate or otherwise include and transform content provided by other web sites. XML is handy but also very complex. Cocoon integrates a number of facilities to help you during your journey through XML-land. One of these is the centralized handling of resolving network resources (e.g. DTDs, symbols, character entity sets, images) to local copies through the use of catalogs. Also explains how to use DocBook DTDs. This example shows the usage of Input Modules in sitemap attribute expressions. This example shows the usage of sources in the sitemap. An example page producing exceptions and handling them. Demonstrates the handler hierarchy and the exception selectors. Some samples of various components that are included with the core, e.g. Stream Generators, Paginator Transformers, Image Readers. Some stuff that does not fit into the other groups of samples. Functionality outside the core has been moved to units called "blocks". This will lead to a more modular Cocoon. Here you find the many samples provided by the currently installed blocks. Since the Cocoon Control Flow is a core technology you find more examples that make use of it e.g. Cocoon Forms block, Petstore block, and Supersonic Tour block. Other examples of Cocoon's control flow of the application. Pages used by HTTP-based automated tests. This page shows the current internal status of cocoon, along with information on the cache and the object stores. Empties the Cocoon in-memory cache. Empties the Cocoon persistent store. Verify that there are no broken hyperlinks in the local Cocoon documentation. This sample will start at the home page of the local documentation webapp and traverse each internal link, reporting its status in a colour-coded table. Be patient - this process will take a while. NOTE: this will work only if you have included the documentation when you built the web application To the front page.