In order to use docbook we need two things: - Someone who puts together a build environment. - A good docbook editor. DocBook XML is really PITA, not comparable to windsor config or NH mappings.
For the latter XMLMind XmlEditor can be used. That one is quite a good WYSIWYG editor for DocBook and it is free for OSS development. However, its output sucks, therefore a buidl environment is necessary. As for the linearity: One output format could resemble the current overview page per project. Once the foundation is laid, it is possible to tweak the templates to get a nice look. As for the history: Docs of released versions should be archived and added to the download archives. Documentation should be part of the project, not part of the website. -Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
