Hi,
> As I said earlier, we can simply add better examples to the existing manual
> via annotations, or we can start from ground zero and create a how-to manual
> for building a dynamic web site.
I'd recommend factoring 2.0 into your plans. In my mind this means, keep
it simple...disclaimer: my ambitious efforts failed so I'm a bit
"slanted."
I think it's important to consider how your interests and needs as a
"user" can be defined as Feature and Tool requests for 2.0. Ami has stated
that he wants 2.0's design and features to be defined from the user's
perspective and that means users like you and I have to step up to the
plate and make the developers aware of our challanges. I believe if the
developers understand our challanges, they'll be able to accomodate our
needs.
I don't believe making the developers aware of our needs is as obvious as
it may appear. We've discussed a process for doing this which amounts to
defining our needs as Requirements prior to coding the Solution. These
documents will clearly describe the feature, and include graphics of the
interface, when appropriate.
The strategy of producing documents prior to code should ease several
challanges; friendlier tools, a basis for documentation and
appropriate information for developers to work with.
This isn't your prototypical adhoc open source strategy but that may not
be an insurmountable challange. If the Requirements define compelling
needs, I suspect the develpers will not be adverse to defining
Solutions in writing and then writing the code.
I've told Ami that I am commited to receiving feature requests and working
with who ever submits them in order to produce usable documentation. In
anticipation of 2.0's content management capabilities, I am writing a
feature request that will be an example of a Requirements document that a
developer can use to produce a Solution. I hope. :)
Well, I'm not really addressing your ambitions with this reply but thought
it would be helpful if you're aware of our thoughts.
Ron
> enrique - trying to make sense out of dynamic web sites with midgard
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
