We should write a "Using Castle" book
("We" in this case meaning "various members of the Castle Community" not necessarily involving me). I see it as one of those Wrox-multi-author-picture on the cover book, with maybe 5 major divisions (Windsor/Monorail/ActiveRecord/DynamicProxy/et al), with each of those having 5-10 chapters. (I'm sure Krzysztof can edit his blog series on DP into 5 chapters in about 2 hours) It will be a great "marketing" tool for the Castle stack, and focus us on bring all our far-flung documention into one place.
Since there’s no real movement here I’m closing it. The documentation page is the de-facto “using Castle” page
So, what about this one? Unfortunately we can't even get people to properly contribute to the documentation on the new wiki...
We tend to use StackOverflow.com for Q&A and google groups for discussions. We tried Zoho Discussion few months back, but although we found it promissing it's not mature enough to make us switch yet.
We're also working on switching our docs to wiki-based platform to make it easier to contribute there.
See my feature request for a Q&A forum:
Castle is not the easiest project to start using.
Cesar Sanz commented
Write various books, One general describing all the castle stack and if possible, one for each project
The first question that would need to be answered would be what level you're wanting to target. If you're targeting someone just coming to Castle MonoRail, then you're wanting to focus on making a functional site using the basic MVC patterns. If you're wanting to target those who would make use of Inversion of Control, then you're talking somewhat more advanced code structuring. Though writing a simple base and then trying to explain why you're adding in Inversion of Control and then walking through the process and what it achieves would make for an interesting piece of documentation.
Agree. Let's discuss it here: http://groups.google.com/group/castle-project-devel/browse_thread/thread/7cd14fed6f591145
I agree that it would be really nice to get people up to speed with a up to date consistent book. Maybe we should consider structuring our docs so that we can build a decent looking ebook from them.
And on a serious note - I think it's a good idea, many projects have their docs in a book-like format and it is nice to read. I am willing to contribute my (edited) tutorial, but DP is small. Writing full in-depth book for Windsor or Monorail is a lot more work...
No, I have a better picture ;) That one is pretty old (2007 I think) but I'm too lazy to change it in each and every place I put it.
If we went with Wrox we'd have this on the cover :)