Did you know you can help improve Cocoon's documentation? Right now, in the most recent CVS release branch and on the live site, you'll find the resources you need to contribute new FAQs, How-Tos, and Code Snippets to the Cocoon project. Specifically:
How to author an FAQ (or set of FAQs) http://xml.apache.org/cocoon/howto/howto-author-faq.html How to author a How-To http://xml.apache.org/cocoon/howto/howto-author-howto.html How to author a Code Snippet http://xml.apache.org/cocoon/howto/howto-author-snippet.html How to submit your contribution via Bugzilla http://xml.apache.org/cocoon/howto/howto-bugzilla.html How to submit your contribution as a Patch http://xml.apache.org/cocoon/howto/howto-patch.html We are taking a deliberately granular approach to facilitate contributions from the widest range of Cocoon users. For example, once guidelines are written, we will announce other types of documents you can also contribute: Recipes, Success Stories, Tutorials, Live Examples, etc. In other words, this is only the *beginning* of a new, community-oriented approach to documentation development. Cocoon is an immensely sophisticated piece of software. At times, however, we all know it can be difficult to grok certain aspects of it. Thus, the more voices that help to explain Cocoon, the better for everyone. Carve out a niche for yourself as an author. If your contribution is useful to others, it will be published the Cocoon's web site! Just as Cocoon provides endless possibilities to build cool stuff, it also affords us an unlimited amount of creative space to write about it. Take a minute to imagine how advanced the Cocoon community would become if each and every Cocoon user took the time to contribute a single, unique FAQ, How-To, or Snippet. Think about it. Diana --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
