One thing to think about is that it may be good to have links so a reader
can jump around. I'm not sure if this can be done with PDF.
Also, are you suggesting to make it downloadable AND part of the user guide?
Thats fine if it can actually stand on its own without references to other
parts of the user documentation.
I still have to create some visuals for this stuff anyway. Also, I need to
do an explanation of the "web.xml" and "struts-config.xml" file contents,
and a very brief but clear, idot-proof, explanation of MVC and how it fits
in struts. This way java develpers who are green behind the ears wont run
away frustrated like they do with other packages and frameworks. The whole
point is that we want EVERYONE to be able to use it and play with it. With
that said, I think you just have to make sure that people can read this
basic information first
----- Original Message -----
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 08, 2001 9:54 AM
Subject: Re: *TED* - round 2 of documentation
> My vote would be to format this as an attractive Word document, convert
> it to a PDF, and post it as the "Struts Brochure". Based on your
> experience, we could move the Struts Component Overview into the User
> Guide, leaving
>
> Struts aims to solve problems ....
>
> Literal explanation of Struts ...
>
> How it all works ...
>
> Activity Summary ...
>
> [ some diagram ]
>
>
> -Ted.
>
