Dear Hussayn, > I am playing around with cocoon for quite a while now in the > role of a "cocoon-user". > After some significant investigation i started writing > down some "usage patterns" that came to my mind while i was > preparing my company website for cocoon.
Nice one. Thanks. Always welcome! :) > Now i want to ask: > > 1.) Is there a repository of howtos concerning cocoon usage? > i know the cocoon wiki, but i only found some very basic > usage pattern descriptions there... Publish them in the wiki. > 2.) If not already existing somewhere... would it be of common > interest to add a "usage pattern" repository somewhere to > the cocoon docs or to the cocoon wiki ? 'Usage patterns' are probably what Leigh and the rest have been refering to as 'best practices'. It's pretty empty at the moment, so you can be the 'trend setter'. Start by publishing them at: http://wiki.cocoondev.org/Wiki.jsp?page=BestPractices The best way to start is to modify the BestPractices page to include a new link to your new (and not yet written) best practice page. I'd suggest a single page for each pattern. E.g. Create the undefined link, and then click on it to create the new page. The point of the wiki is to get the information to the cocoon community quickly without a lot work. As the wiki site evolves, it periodically gets re-arranged. Don't worry too much about the organization until you publish your initial material. Moving stuff around later is fairly easy (and everybody has an opinion, about the organization. You are one of the few willing to contribute content! :). > Is there anyone "responsible" for this or could anyone tell me, > how to proceed, e.g. where to post my patterns once they are > ready to publish? We're all reponsible... including you. :) Just ask the list if you need more help. Best wishes and thanks, Alan. --------------------------------------------------------------------- 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]>
