Migrate wiki into project

[0xazure]

Move wiki documentation into a project subfolder docs/.

Closes #635.

[0xazure]

I would be open to discussion regarding the series of commits from the wiki repository history, given how many of them there are.

Post-merge TODOs:

• Clean out wiki repository & redirect to docs/ OR remove wiki entirely (via GitHub project settings)

[invalidCards]

@0xazure Might be an idea to just squash it all under the header of "Merges wiki into main project"

[Wolvan]

I agree with @ThePsionic

[0xazure]

I suppose the question would be if we care at all about the edit history of the wiki files. There's a few more recent ones that should probably be kept in the history, like pretty much anything after new-xkit took over.

[invalidCards]

I personally don't really care about the edit histories of the wiki.

[hobinjk]

I don't mind having the edit history available. It's nice to see who to blame for writing specific lines, especially if those lines appear to be wrong.

[nightpool]

• we should keep histories
• they would show up in git log basically when they were created right? because default order is reverse chronological?
• I'm down with removing the wiki altogether but we should make sure that the docs get into our gh-pages in rendered format somehow eventually.

[0xazure]

show up in git log basically when they were created

I believe so, yes. They won't all get pushed to the top of the history if this is merged.

make sure that the docs get into our gh-pages in rendered format somehow eventually

Not sure I follow with this. @nightpool you mean you'd like to see all docs/**/*.md files added to gh-pages as HTML-rendered files? I'm not sure I see the need for this, given that Markdown is pretty readable in its own right. GitHub will also automatically render any pages you view in the web UI, so seeing HTML-formatted documentation pages would be as simple as viewing the docs/ folder on GitHub.

[0xazure]

@nightpool still waiting on a reply for the above.

[nightpool]

Must have totally missed that reply around the end of the term.

I'm fine to merge for now I was more thinking about long term stuff.
On Fri, Nov 13, 2015 at 8:29 PM 0xazure notifications@github.com wrote:

@nightpool https://github.com/nightpool still waiting on a reply for
the above.

—
Reply to this email directly or view it on GitHub
#695 (comment).

[0xazure]

I see most of the documentation in this PR being eventually superseded by generated JSDoc documentation, which we would want to host through gh-pages. This is more an effort to get the docs in sync with the project as a whole; we can evaluate how we want to handle new documentation on more recent pieces of the codebase separately.

[nightpool]

Yeah definitely. Didn't mean to confuse this pr with my long term
speculation.
On Fri, Nov 13, 2015 at 9:08 PM 0xazure notifications@github.com wrote:

I see most of the documentation in this PR being eventually superseded by
generated JSDoc http://usejsdoc.org/ documentation, which we would want
to host through gh-pages. This is more an effort to get the docs in sync
with the project as a whole; we can evaluate how we want to handle new
documentation on more recent pieces of the codebase separately.

—
Reply to this email directly or view it on GitHub
#695 (comment).

[bvtsang]

LGTM, thank you very much!

@homu r+

[homu]

📌 Commit aec9a54 has been approved by bvtsang

[homu]

⌛ Testing commit aec9a54 with merge a1f8e42...

[homu]

☀️ Test successful - status