ok
----- Original Message -----
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 6:14 AM
Subject: Re: *TED* - round 2 of documentation
> At some point someone proposes something in a final form that can be
> committed directly to the distribution.
>
> We're all volunteers here, and share suggestions about what we each
> would like, but what anyone actually does is up to the individual.
>
> Once something is done, and ready to ship, or at least test in a
> proposed final form, then we decide to commit it to the distribution.
>
> (At this point, the only document submitted is not in a final form,
> and so it's not possible to make a decision.)
>
> If you wanted to send me a Word document in a final form, I could
> convert it a PDF and make it publically available (if you agree that
> making this a PDF is a good idea).
>
> Jonathan Asbell wrote:
> > Ok so whats next?
> >
> > ----- Original Message -----
> > From: "Ted Husted" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, July 08, 2001 10:30 AM
> > Subject: Re: *TED* - round 2 of documentation
> >
> > > We can hyperlink within a PDF. I was thinking it would be listed on
it's
> > > own above the Users Guide, so people would tend to read it first.
> > >
> > > Home
> > > Brochure (PDF)
> > > Users Guide
> > > Resources
> > > Who We Are
> > > Installation
> > > Release Notes (nightly)
> > > Release Notes (1.0)
> > > TODO list (1.1)
> > >
> > > But to keep the brochure non-technical, we should probably move the
> > > Struts Component overview into the Users Guide. Especially since you
> > > mentioned that this part wasn't helpful to your developers as part of
a
> > > quick start. ("Struts in a NY minute" ;-)
> > >
> > > I agree that the installation page should be refactored, but we might
to
> > > keep that separate from the brochure.
> > >
> > > As mentioned, I would especially like to see the installation
> > > instructions turned upside down, so that people are encouraged to
start
> > > with the WARs, Struts JAR, and the blank application before trying to
> > > build it from scratch. In practice, I'd say most people may write an
> > > application or three before needed to actually build Struts for
anything
> > > (if ever).
>
