Contributors cannot edit the wiki (or it's unclear how to)

[Tyriar]

I can clone the wiki, as far as I'm aware though GitHub does not support PRs for wiki repos.

Related #414, #556

[Tyriar]

Since we want to review changes to the wiki I suggest we handle documentation the way Chromium does now; a git repository full of .md files (using jekyll?) to enable community contributions.

[Tyriar]

Another issue with using a wiki over a repository; images need to be uploaded somewhere separate from the wiki as GitHub doesn't support images on the wiki like in issues. #4799

[Tyriar]

@Microsoft/vscode is anyone opposed to including the documentation in the main repository under ./docs (or ./doc, ./documentation, etc.) and turning off the wiki all together? This would help fix these issues with the wiki and potentially also improve the visibility of the developer documentation.

It can still have roughly the same structure:

• ./docs/welcome.md
• ./docs/project-management/...
• ./docs/contributing/...
• ./docs/documentation/...

[Tyriar]

One problem with doing this is that the table of contents would be manual.

[Tyriar]

@egamma @seanmcbreen @waderyan

[waderyan]

I am in favor. I can't think of any down sides. We still have control over the content and can accept help with PRs.

[chrisdias]

double check with @egamma as he does most of the wiki edits. we will need to update the wiki to point to the appropriate folder.

also, should we call it the /wiki folder instead of /docs, to avoid confusion with vscode-docs repo?

[egamma]

In favor in general, but is there any migration overhead to get existing wiki contents over to plain md? For example, do we have to convert wiki links to mark down links.

The wiki tab is popular and we need to ensure that the wiki in /wiki is as easily discoverable.

[Tyriar]

There's a little migration overhead for the internal links ([[Issue Tracking]] becomes [Issue Tracking][issue-tracking.md]).

Another solution is to keep things as is and detail how to contribute to the wiki in the how to contribute page. This could be submitting an issue with the edit for small edits, for larger edits clone the repo and create an issue asking for it to be merged into the real wiki.

[Tyriar]

@egamma @chrisdias @waderyan I did a very rough migration on my fork, let me know how you feel about it https://github.com/Tyriar/vscode/tree/wiki/wiki

Some things to point out:

• The horizontal width of the container is larger, making for better image viewing https://github.com/Tyriar/vscode/blob/wiki/wiki/contributing/how-to-contribute.md#using-the-chrome-developers-tools
• Just going to ./wiki will show the welcome page as it's the README.md
• No more dependency on imgur https://github.com/Tyriar/vscode/tree/wiki/wiki/contributing/images

[waderyan]

I like it @Tyriar