|
Friday 13 June 2003 11:18:00 am
Dear Bård,
The structure you propose is from a developer point of view addressing the needs of different audiences simultaneously. I think at least you should put something like "Start here" to the top which guides the different groups of end-users. This should contain:
- definitions of what is a CMS from the ezp point of view,
- the fact that ez publish is also a powerful develoment framework (like you do slightly in the presentations on ezp by explaining the architecture)
- !!what to do to according to different *scenarios* that correspond to the the profiles of end users!! From what I learned over the past 1.5 years on these forums and the needs at various organisations, these *scenarios* can be reduced to: - building a dynamic web site where few people can post articles and similar content, but where lots of others can "participate" through forum-like things (including comments, annotations, ratings, ...). This is where the 2.x series are strong out of the box (and covering probably 60% of ezp end-user needs) and in this way you provide a transition for 2.x users too. You may want to include some basic templates to start from (the demo does not fulfill this goal, they are OK for developers who want to learn ezp3 without docs). - building intranets/extranets for small and large organisations where you explain the flexibility of the templates, classes, sections, rolse, .... Here you (or we) should provide the pointers to specific and in-depth documentation on templates and the possibilities of the other components illustrated with "real-life" examples. Examples are very important and should contain ready to use as well as more abstracted ways of explaining functionality - advanced development: going beyond the traditional use of CMS and intranet/extranet sites. Here you should explain the priciples and architecture behind the various kernel modules, how to build your own modules, how to keep ezp releases in sync with your own development, .. Here some of the ezp community members need to help you since you may not be fully aware of the potential applications of ezp3. In one sentence: "The docs should reflect the needs of end-users in a layered fashion; from simple to complex uses and from basic to very powerful features of the various ezp3 components." In this way you can both provide an answer to current needs of end-users and let them even discover solutions to problems they were not even aware of. Enjoy your weekend and thanks again for your hard work! --paul
eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans
|
