Separate scope and responsibility of whitepaper and wiki pages

[riobard]

It seems now we have an official whitepaper whose content is mostly mirrored from the wiki pages. May I suggest that we separate the responsibilities of the two to avoid the need to keep both in sync?

I propose the following split:

• Whitepaper for official protocol specification in RFC-style.
• Wiki pages for guides, tutorials, and other helpful content.

Additionally, we need to come up with a better strategy to generate the content of the official website. It's less than optimal right now due to case-sensitivity of file paths. (Maybe this needs another issue to discuss?)

[Mygod]

I think the current content is more fit as a protocol specification rather than a white paper...

[madeye]

Contributions are welcome, you know, I just converted the markdown pages to PDF...