Separate repo for content

I personally like the model of storing content in a Github repository (for text content, like WhatToCode will have), and the allowing for pull requests to add content. You can easily manage changes this way, and with a little automation you have new content/edits accepted automatically.

This doesn't have to get in the way of having an online management interface as well, as this can be set up to store changes in git.

It also has the upside that (when you add a license) it's easy to get the dataset to play with, and it allows for easier forks of the site (which I believe is a good thing, so that in case the project goes sour the data is still of use to someone).

[arieltorti]

Indeed that's was I was planning to do , and that's why I need the help of the people in order to make this project viable