Some background for what's worth: - In the previous wiki style things were just too disconnected. Works fine for wikipedia but not for something that might need to have a reading order - There was an attempt to keep each article on the new format very short. This is pure usability. If people see a long scroll they feel it's gonna take too much time to read and leave. This is especially true for the getting started sections - The format and organization was inspired by apache httpd documentation - Keeping documentation for older versions was also inspired by the apache httpd documentation and a book suggested this approach as well. I think the book was "Producing Open Source Software" - I sincerely dislike the docbook style, but I'm willing to give it a try. Never really liked the way NHibernate and Spring are documented. - The anakia style is also an attempt to keep formatting/layout separated from the docs. I think that was successful, but it does make contribution more difficult.
-- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
