First : Thanks ricardosanX !
I’ll most definitely read it and if I find the time, might translate it in french.
About the wiki discussion
, this is funny you should mention this. We have similar discussion
at textpattern’s forum about the wiki, TextBook. I take care of the french doc here, and both english and french docs are not moving forward as they should while the community is very active and IMHO, talented. I am mentionning all this because when I came here, I had the sense that this community shared many common point with textpattern’s.
Anyway, my take on this is that wikis are powerful tools
and one of the things I like that most CMS don’t have is revisionning. Also, a wiki like MediaWiki handles multilingual content very well. Not to mention TOC auto-generation which is nice. As Jason said, the WordPress Codex is one good example of sucessful wiki documentation (and about structuring the doc : see how it is user-oriented).
Yet, from a community point of view the efficiency of wikis depend of its adoption by those who will write for it.
It’s key to set up a tool that will make writers want to contribute. In the end, features is not what will make a documentation project a success. People are.
With that in mind, you can make a choice. I like the idea of buiding something around MODx and I agree with Jason about the editor : more often than not that’s what you use to write and if it doesn’t fit for you, you probably won’t write. About Textile, I have been using it ever since I adopted Textpattern : it’s a cool syntax you’ll learn quite fast, less cluttered than the wiki syntax. But some people won’t click with it : some prefer Markdown
. Some prefer WYSIWYG. It would be great to be able to choose.
Just for reference, Instiki is a simple yet efficient wiki featuring Textile, but it’s Ruby On Rails and I don’t know if a MODx integration would be doable...