ASF_20_SRC_AUTO/src/documentation/xdocs/plan/doc.xml - cocoon - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">

 <document>
  <header>
   <title>About the Cocoon Documentation Effort</title>
   <subtitle>Overview</subtitle>
   <authors>
    <person name="David Crossley" email="crossley@apache.org"/>
    <person name="Diana Shannon" email="shannon@apache.org"/>
   </authors>
  </header>

  <body>
  <s1 title="Overview">

   <p>
 There is a concerted effort underway at this time to improve Cocoon's documentation. This effort is based on the belief that open source documents can be as first-rate as the software on which they are based. However, such an endeavor is entirely dependent upon vital and timely forms of contributions from developers and users alike. Make no mistake about it; everyone is needed and invited to participate in this effort!
   </p>
   <p>
 While we have a lot to do, there are evolving structures in place to facilitate and enhance your efforts. We have numerous guidelines for authoring documents, a document-specific email list, and a complementary documentation architectural project at <link href="http://xml.apache.org/forrest/">Forrest</link>. If you choose to become involved, you will discover many like-minded developers and users who care about Cocoon documentation and will support your effort. Here are a few ideas to help you get started.
   </p>

   <s2 title="Cocoon Docs List">
 <p>
 Find out what documentation efforts are already in process among other users
 and committers. Consider joining the
 cocoon-docs <link href="http://cocoon.apache.org/community/mail-lists.html">mailing list</link>.
 </p>
   </s2>

   <s2 title="Forms of Document Contributions">
   <p>
 Check out Cocoon's How-To guidelines to learn about the variety of ways to contribute or improve Cocoon documents.
   </p>
 	<ul>
 <li><link href="../howto/howto-author-faq.html">How to Author an FAQ</link></li>
 <li><link href="../howto/howto-author-howto.html">How to Author a How-To</link></li>
 <li><link href="../howto/howto-author-snippet.html">How to Author a Code Snippet</link></li>
 <li><link href="../howto/howto-author-core-docs.html">How to Author Core Documentation</link></li>
 	</ul>
   </s2>

   <s2 title="Cocoon Wikis">
   <p>
 Cocoon has two promising and complementary wiki efforts underway.
 </p>
   <ul>
   <li>
 <link href="http://wiki.cocoondev.org/">Cocoon Wiki</link> focuses on content development for the Cocoon project. It is designed to facilitate document development and collaboration from all levels of Cocoon users. Documents include FAQs, snippets, how-tos, tutorials, RTs (random thoughts), dreams, surveys, and more. The preliminary focus of this the wiki is to serve as a documentation "breeding ground," where docs can "grow" until mature enough to become official cvs docs. However, it already represents a lively and valid document resource in its own right.
   </li>
   <li>
 <link href="http://www.anyware-tech.com/wikiland/">Wikiland</link> is an ongoing development effort to build a Cocoon-based wiki architecture. Wikiland features a Cocoon dictionary as the pretext to use, test and develop the wiki. The project is seeking Cocoon-oriented developers to further its development. For more information, see the <link href="http://rossel.free.fr/" >Wikiland home page.</link>
   </li>
   </ul>
   </s2>

     <s2 title="Other Information">
   <p>
 If you're interested in reviewing recent documentation additions or substantive modifications, see the documentation <link href="changes-doc.html"> History of Changes</link>. You may also want to check out the documentation-specific <link href="todo-doc.html">To-Do List</link>. You can also take an advance look at a proposed <link href="proposed-toc.html">table of contents</link> for a revised Cocoon guide. You may also be interested in reviewing some <link href="issues-doc.html">general and specific issues</link> related to Cocoon documentation. Your comments and feedback on any of the above are welcome on the cocoon-docs list.
   </p>
   </s2>

  </s1>


  </body>
 </document>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">

	<document>
	<header>
	<title>About the Cocoon Documentation Effort</title>
	<subtitle>Overview</subtitle>
	<authors>
	<person name="David Crossley" email="crossley@apache.org"/>
	<person name="Diana Shannon" email="shannon@apache.org"/>
	</authors>
	</header>

	<body>
	<s1 title="Overview">

	<p>
	There is a concerted effort underway at this time to improve Cocoon's documentation. This effort is based on the belief that open source documents can be as first-rate as the software on which they are based. However, such an endeavor is entirely dependent upon vital and timely forms of contributions from developers and users alike. Make no mistake about it; everyone is needed and invited to participate in this effort!
	</p>
	<p>
	While we have a lot to do, there are evolving structures in place to facilitate and enhance your efforts. We have numerous guidelines for authoring documents, a document-specific email list, and a complementary documentation architectural project at <link href="http://xml.apache.org/forrest/">Forrest</link>. If you choose to become involved, you will discover many like-minded developers and users who care about Cocoon documentation and will support your effort. Here are a few ideas to help you get started.
	</p>

	<s2 title="Cocoon Docs List">
	<p>
	Find out what documentation efforts are already in process among other users
	and committers. Consider joining the
	cocoon-docs <link href="http://cocoon.apache.org/community/mail-lists.html">mailing list</link>.
	</p>
	</s2>

	<s2 title="Forms of Document Contributions">
	<p>
	Check out Cocoon's How-To guidelines to learn about the variety of ways to contribute or improve Cocoon documents.
	</p>
	<ul>
	<li><link href="../howto/howto-author-faq.html">How to Author an FAQ</link></li>
	<li><link href="../howto/howto-author-howto.html">How to Author a How-To</link></li>
	<li><link href="../howto/howto-author-snippet.html">How to Author a Code Snippet</link></li>
	<li><link href="../howto/howto-author-core-docs.html">How to Author Core Documentation</link></li>
	</ul>
	</s2>

	<s2 title="Cocoon Wikis">
	<p>
	Cocoon has two promising and complementary wiki efforts underway.
	</p>
	<ul>
	<li>
	<link href="http://wiki.cocoondev.org/">Cocoon Wiki</link> focuses on content development for the Cocoon project. It is designed to facilitate document development and collaboration from all levels of Cocoon users. Documents include FAQs, snippets, how-tos, tutorials, RTs (random thoughts), dreams, surveys, and more. The preliminary focus of this the wiki is to serve as a documentation "breeding ground," where docs can "grow" until mature enough to become official cvs docs. However, it already represents a lively and valid document resource in its own right.
	</li>
	<li>
	<link href="http://www.anyware-tech.com/wikiland/">Wikiland</link> is an ongoing development effort to build a Cocoon-based wiki architecture. Wikiland features a Cocoon dictionary as the pretext to use, test and develop the wiki. The project is seeking Cocoon-oriented developers to further its development. For more information, see the <link href="http://rossel.free.fr/" >Wikiland home page.</link>
	</li>
	</ul>
	</s2>

	<s2 title="Other Information">
	<p>
	If you're interested in reviewing recent documentation additions or substantive modifications, see the documentation <link href="changes-doc.html"> History of Changes</link>. You may also want to check out the documentation-specific <link href="todo-doc.html">To-Do List</link>. You can also take an advance look at a proposed <link href="proposed-toc.html">table of contents</link> for a revised Cocoon guide. You may also be interested in reviewing some <link href="issues-doc.html">general and specific issues</link> related to Cocoon documentation. Your comments and feedback on any of the above are welcome on the cocoon-docs list.
	</p>
	</s2>

	</s1>



	</body>
	</document>