MCServer Wiki / Book

[LogicParrot]

We aren't Debian, I don't think we need the seperation of a "startup guide" and an "advanced features guide". I believe it all fits in one place.

@bearbin, I don't agree with some of the pros/cons:

• We can resolve the Wudles issue and arrange a more decentralized management.
  
• The Wiki is definitely easier to search, regardless of Google. A wiki enjoys a search engine and an ability to have page redirects (e.g. searching for "configuration" can redirect to the "ini files" article).
  
• The coherent voice issue is something any group-written documentation might suffer from if not managed properly, that includes the book.
  
• The Wiki does not have to be an information dump. It can be a sliced version of the well-arranged book. And the homepage can be the Book's table of contents.
  

I'm in favor of a mirroring approach. Forget "the Wiki" and "the Book". There'd be only "the guide", available in several forms: A single-paged version, a sliced version (happens to be hosted on a Wiki), a PDF, perhaps even a Kindle. Contributions to that guide happen to be Wiki-style, but they're reviewed for coherency and compatibility with the Table of Contents structure as strictly as a git PR. Note that this review necessity is present regardless of the choice, so my proposal does not incur any management overhead.

As far as I can see, this approach has no disadvantages whatsoever, and it enjoys the advantages of both the Wiki and the Book.
If Wudles is unresponsive, we could even set up a new one, so the Bus Factor isn't an issue.