Wow George, that's a cool concept! Thanks for setting up the look & feel preview!
Bpod's documentation would definitely benefit from version control and some way of supporting curated user contributions.
I'm also in favor of a more future-proof host (e.g. github). Last year Google sites forced an update to their new version of the product. Their auto-migration tool made a huge mess of the Bpod and Pulse Pal wikis, and it took a few days of manual editing to fix it. There's no saying when they'll do something similar, or discontinue Google sites entirely.
I'm admittedly not familiar with markdown (github flavor or otherwise). It looks like there's a small learning curve to traverse, which shouldn't be much of a problem for us at Sanworks.
Unfortunately I won't personally be able to contribute to this for a while. With our small R&D team, we're working at full capacity to overhaul Bpod's Python software, with an anticipated release at year-end. Bpod's dependence on MATLAB is a major bottleneck for adoption of our platform beyond our current user base, and complicates integration with emerging software tools. Once we have working Python software, documentation and tutorials will be at the top of the stack.
I'm definitely interested in a documentation scheme like what you've put together in the long run, so the verdict is don't shelve it! If you have bandwidth to contribute more, I'd be more than glad! I'd also be glad to meet sometime if you'd like, to talk through some ideas. Let's follow up by Email - email@example.com