Sure Ted. Thanx. My perspective always comes from assuming that the reader
doesnt know much. People get confused and sidetracked with jargon, and
struts can be used by less experienced people if explained correctly. I
mean, dont we want the user base to grow so it can be developed better and
faster =)
We ant users to "get it".
We dont have to explain MVC as much as we have to explain them about
Struts. The sell is the framework and its capabilities. Lets talk to
people in street English so when their superiors want to know about it its
not too hard. After all, its the superiors who actually say yes or no to a
technology, and many are afraid (it took 2 months for the senior engineer at
my place to even LOOK at Struts, and he is no dummy)
----- Original Message -----
From: "Ted Husted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 21, 2001 6:52 AM
Subject: Re: I would like to offer myself to help with documentation
> I like the idea of a "brochure-size" introduction to Struts, and a
> "quick-start" installation guide. I think this might make a useful
> preamble to the User Guide.
>
> My favorite part is where you say:
>
> "Your company has decided"
>
> I think this would make a nice focal point for an introduction. After
> all, the framework (like all applications) is really suppose to be
> solving a given set of problems. But right now we seems to assume that
> everyone knows what problems MVC is trying to solve, and go off from
> there.
>
> So, I'm thinking starting out with something like
>
> "Your Web team wants add a new section to the site" ...
>
> "Your team leader decides that Scriplets are a Bad Thing" ...
>
> "Your Web Application must be internationlized" ...
>
> "Your application must be accessible to everyone using anything from
> anywhere" ...
>
> "Your application must be J2EE compliant and make good use of Enterprise
> Beans" ...
>
> I could try refactoring the draft, if you agree.
>
> -Ted.
>
