The rest is to learn the Cocoon. What I propose is to read everything in 'User documentation', even though in the beginning you don't need 80 % of functionality.
Cocoon framework is so unique and powerfull that it is very good to learn the ideas and ready components to avoid doing simple jobs in stupid ways (especially when you worked before with
other technologies - jsp/php). For example one guy from our team introduced completely new way of handling internationalization texts (which was of course shitty comparing to Cocoon's i18n) - mainly due to not reading documentation.
And I can say, Cocoon docs are really good - only the newest stuff which comes with unstable blocks are not yet documented fully.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
