Hi,
I would like to contribute to the great documentation effort started by
Ulrich and Robin as designer. I have seen all the work done to migrate the
existing documentation to confluence and macro to identify deprecated
documentation.
Will the documentation continue to be generated from xdoc and apt files, or
will it be fully maintained via confluence ?
Actually this WE, i have started to think on what should be the plan for a
reference guide and how to organize chapters. We have a lot of starters for
new comers but in my opinion with User guides, we miss to many existing and
interesting informations because of the lack of a structured TOC.
This thought has lead me to this simple (and sorry if it sounds stupid)
question : What is Tapestry 5 ?
In fact, tapestry-core corresponds to the module we use to build Web
applications, then 'core' Tapestry is Web application development. After
that i made a quick overview of modules present on trunk to get familiar
with fresh developments, here is the list :
we have the most popular and most used :
- tapestry-ioc
- tapestry-spring
- tapestry-upload
- tapestry-hibernate and hibernate-core
- tapestry-test
but also
- tapestry-func
- tapestry-beanvalidator
- tapestry-jmx
- tapestry-webflow
+ all the existing third party libraries...
My conclusion is that Tapestry is really so much more than a Web Framework
and the IOC is central.
So to design the plan,
Should i address IOC first and then talk about web application development
as any other part of the documentation ?
or
Should i emphasize on the Web development and make it central, and give a
plan for every contribution ?
Anyway i would be pleased to contribute to the documentation effort for my
first contribution as committer, so suggestions are very welcome.
--
Regards,
Christophe Cordenier.
Committer on Apache Tapestry 5
Co-Creator of wooki @wookicentral.com
