+ 1 on the documentation re-org, with one caveat: Less is more, sometimes. Especially when one aspect of the documentation is covered in multiple places. Such as when one guy covers it this way, and then another guy comes back months later and hits it from a different perspective, and both views are on left on the site. This happens to a lot of open source projects.
Simplicity and precision make things easier to follow, which is quite a challenge when things are moving as rapidly as Avalon. You guys are really kicking some butt. Major kudos. Leo Simons wrote: > > I propose we re-organise documentation a bit. > > I'll start with the framework documentation. > > Suggestion: > > - Essentials > - Overview > - Features > (new) > - Getting Started > (new) > - Downloads > > - Guide > - OOP best practices > (modified reuse-standards.html) > - What are Patterns? > (modified from patterns.html) > - Patterns in Avalon > (modified from "Patterns and Design") > - What is COP? > (modified from "The Api") > - COP in Avalon > (modified from "The Api") > - Where to go from here > (link to "Developing with Avalon") > > - Reference > - Api Docs > - Diagrams Docs > - The Lifecycle > (new) > > - For Developers > - Changes > - Coding standards > - Project structure > - CVS > - Mailing Lists > > After your comments are integrated into this, > and there are no -1s, I will make all the > required changes as soon as I have time. > > - Leo > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
