A discussion would be appreciated: 
1) Every feature in the Features List  should contain only a short description what the feature is and not how to use it (see for example Page Editing). At the end there must be just a link to the related documentation.
2) All documentation pages should be placed in the same wiki, currently it's not the case.
3) The current FAQ page is not really the FAQ most users get used to use, therefore I haven't included this page here. Probably all useful tips can be moved to Cookbook (HowTo) pages. And for user questions the mailing list should be used instead (or a users forum in the future...).

Have you seen the Features list already? Then depending on what you want to do, choose the guides below. If you want to improve the documentation see how you can do that in the Documentation Guide.

Basic Usage

XWiki is first and foremost a standard wiki. You might want to read up on the definition of a wiki. This section of the documentation will show you how to use all the basic features of XWiki. At the same time as you follow the guides below we recommend that you try out what you learn on the Playground. This is a XWiki instance that we've set up for you so that you can easily discover the joys of using a wiki.

• Editing Pages 
• XWiki Syntax 

Understanding XWiki

• Basic Concepts 
• Document Lifecycle 
• URL resolution 

Advanced Usage

That is what the second generation wiki means

• Programming in the wiki  remark: the name "Developer Guide" is confusing, because the first impression is, it's about developing of the XWiki platform
• Code Zone 
• User Cookbook 

Administration

• Installation 
• Common Configuration 
  • Skins
  • Changing Color Theme with default skin 
  • Encoding
  • Logging 
• Access Rights 
  • User Management 
  • Group Management
  • Authentication (LDAP, Database...) 
• Backup/Restore 
  • Import/Export pages 
• Security tuning 
• Performance tuning 
• Virtual Wikis 
• Clustering 
• Administrator Cookbook 

Further information

• User mailing list 
• JIRA (planned features, reported bugs, workarounds) 

 Therefore I would suggest to disable the comment feature for final/public documentation. But for drafts it can be really useful.