The documentation point is often raised and of course it is never enough documentation and a book like writing that guides carefully through tapestry would be really great.
However I think that the available documentation is still very, very good. Most of the things I need to know I find in the regular docs. If that doesn't help the javadocs are extremely helpful. There aren't that many open source projects that have such a decent documentation. I have to confess that I sometimes have to browse a couple of pages before I find the information. Maybe an integrated search in the site would help On Fri, May 1, 2009 at 7:39 PM, Ulrich Stärk <u...@spielviel.de> wrote: >> Nobody likes to do documentation. That's a problem in a volunteer >> effort. If Tapestry's committers reported to me, I'd be parceling out >> the kind of documentation you're talking about. That's not how it >> works. > > Why don't you create JIRA issues for those documenation tasks? This would > show that documentation is as important as improvements/bugfixes and > enhances Tapestrys overall quality. This could also lead to the community > being able to contribute something to the framework. I for one like to pick > myself some simple issue like localizing message catalogs or improving > documentation and contribute and I could imagine that others might do the > same. > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
