Hi Bryn, Thanks for your feedback, lots of good points. See below for a point by point comment. I’ve just sent another email explaining more the context and the reason for this initiative. The goal is of course to be as unbiased as possible although it’s never fully possible to do so. At least we need to find out the parts that are not correct and remove them or word them better. The goal is to highlight the strengths of XWiki vs Confluence and MediaWiki. I agree that I’m not sure we need to list the stuff that are similar and maybe it would be better to only mention the differences. Now that said, I think the idea is also for neophytes to wikis to be able to understand this page. We need to decide which we wish to have. You seem to be knowing Confluence which is great, since it’s been more than 10 years that I haven’t used it myself. Indeed, I don’t know why there’s this "Ticket plugin” mentioned. I’ll check with Caty. XWiki certainly doesn’t have a full ticket extension right now AFAIK. The closest I can think of is the Task Application: http://extensions.xwiki.org/xwiki/bin/view/Extension/Task+Manager+Applicati… Definitely. I’ve also discussed this with others and it’s time that we start curating extensions and introduce some “Editor Picks” or “Recommended” extensions. I’ll start this in another thread real soon. Agreed. Maybe the polyglotism too (ability to use various markup syntaxes). Could you explain why it’s simpler with Confluence by comparison with, say, XWiki 7.4.3? I think this now at least as easy if not more now. Same for access restrictions to children pages. See http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization This is not fully correct. A lot of new APIs have been introduced, showing the dynamism of the XWiki community indeed. However, we take very seriously backward-compatibility (so seriously that breaking it fails our build automatically ;)). So all that worked are still supposed to work. Do you have an example that you’ve noticed where it’s not true (it can happen from time to time when we conscientiously decide to break a recent API that we think nobody uses) . Any example? That would help to fix them. It’s certainly true that we need to improve on dev documentation (the user doc is probably ok but the dev one can be improved). Well our goal is to be open source and still be good on all fronts! :) Re Confluence, they have lots of people working on the doc vs XWiki where it’s the developers doing it, so it’s more a question of manpower than of proprietary vs open source IMO. What’s interesting though XWiki is a smaller team, we’re still progressing and innovative at least as fast (if not more) as Confluence IMO. Lots of people have commented that they prefer XWiki over Confluence. Some quotes are on https://www.xwiki.org/xwiki/bin/view/References/Testimonials Anyway, let’s focus on editing this comparison page to make it as accurate as possible. Keep the comments coming and feel free to edit the doc too if you wish. Thanks -Vincent