My point is creating a simple and small page was that almost all users are interested in Trinidad, instead of the plugins. The JDev plugin might be the most interesting one, which can be used outside of Trinidad. The archetype might be also interesting for "getting" started.
But anyway, I'll put a src/site (with xdoc) to *each* of the modules and *remove* the site module. I try to keep it as small as possible, since we need (basic) documentation for getting the release done. I will not care about special skinning etc (feel free to provide patches etc). The release is more important than having a good looking page... b/c without the plugins release, there is NO release of Trinidad (since it depends on SNAPSHOTS). Regarding the archetype, I remove the Jetty6 plugin (snapshot) and will come with a basic documentation for getting Jetty6 to work. That Jetty plugin is pretty neat, since "mvn jetty:run" starts a webcontainer and deploys the app. I hope, all of you agree ;) -Matthias On 8/15/06, Adam Winer <[EMAIL PROTECTED]> wrote:
I think that we should just have links from the plugin site to the Trinidad site and vice versa (and probably start people off on the Trinidad site, because that's what 99% of people will want). No need for an umbrella site. -- Adam On 8/15/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > ok, sounds good. > > so, do we want a "src/site" under *plugins* folder, as our entry point? > http://svn.apache.org/viewvc/incubator/adffaces/trunk/plugins/ > (of course, each modules has its own src/site) > > That's for the plugins. > > Howto do we handle the "integration" with Trinidad? > > I think it would be nice if the user has the possibility to reach both > (Trinidad and Plugins) from a starter site (i.a.o/adffaces OR > m.a.o/trinidad) > > -Matthias > > > On 8/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I always prefer compositon, I find it easier to maintain and it's also > > easier to add/remove parts imho. so +1 for option 2. > > > > > > Regards, > > > > Simon Lessard > > Fujitsu Consulting > > > > > > > > > > > > "Matthias Wessendorf" <[EMAIL PROTECTED]> > > Sent by: [EMAIL PROTECTED] > > 2006-08-14 23:41 > > Please respond to adffaces-dev > > > > To: adffaces-dev@incubator.apache.org > > cc: > > Subject: [plugins] documentation > > > > > > Hi, > > > > this email contains two things. > > > > a) Call for help on documentation: > > If you like to provide some documentation about the Trinidad plugins, > > feel free to add content to the wiki. Or provide xdoc or apt patches > > ;) > > > > b) Structure: > > There are two options for handling the doc structure: > > 1. create a site module, which contains *all* documentation > > 2. having each (sub)project/plugin having it's own src/site and > *compose* > > it. > > > > Shale uses the first (for instance). See [1] for David Geary's remote > > example. MyFaces uses the second. > > > > What do you like more ? > > > > -Matt > > > > [1] http://shale.apache.org/features-remoting.html > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://jroller.com/page/mwessendorf > > mail: mwessendorf-at-gmail-dot-com > > > > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
-- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
