Right. As we discussed on Slack - here's my take away from that conversation.
Wikis should not substitute real answers or try and collate multiple answers into one "answer all" answer. We want the diversity of multiple questions. We also want the gamification aspect of adding new valuable input to an already answered question - and being rewarded for doing so.
That said, CWs are appropriate when
- The subject matter is unreasonably large to compile for any one person. A community effort is required.
- The subject matter is "dynamic" in nature. Like information that updates often, and preferably should be a community collaborative effort to maintain.
As an experiment (and to try and broaden our scope), I added 2 CWs this week. Both have been very well received by the community - lots of Tweets and so on. The first moreso than the second, but I believe this boils down to "not enough good information in the wiki" for that one. (personal opinion)
How can I connect with the Sitecore Community?
How can I get started learning Sitecore?
I think we agreed (at least on the first one) that this is exemplary for, when a CW is appropriate. No one person should be expected to keep the list of UGs up to date, for instance. Also the "Community Resources" will expand over time.
I think I captured the gist our conversation here. Else throw a comment if I omitted or got something wrong :-)