The documentation should follow the learning curve. May be each doc should have a requirement section, which lists all the notions that must be well known to understand the current topic. And docs should be rated under a system of "Beginner", "Intermediate" and "Advanced" topics.
In fact, i think everybody should use wikiLand : http://www.anyware-tech.com/wikiland I promise that if someone else than me posts something on wikiLand, I code the XSLT to export to xdocs :-) That's a deal, dudes! The second thing that makes Cocoon obscure is the lack of intuitive debugging system. An intuitive debugging system allows the user to _see_ the behaviour of the program. I think that a Cocoon app which could display on the client how the sitemap resolved for a given URI, which could allow to browse between a sitemap resolving report and XML/XSL files involved in the resulting pipeline, all that would make newbies get into Cocoon more easily. The first step should be an easy step. And last thing, error management should be heavily handled in Cocoon. No more strange messages on the client side. My humble 2 cents. --------------------------------------------------------------------- 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]>
