Improve documentation for users and developers

[jyeatman]

AFQ-Browser documentation should be improved to include more information to support other developers in incorporating AFQ-Browser into their software projects.

[arokem]

Use doctr to automate documentation build

We do also need to add content:

• Data specification.
• How would I use this with data from another software (not AFQ)?
• How would you contribute to this project?
• Python API
• What are things that you can switch out, if you want to?
• Link to the preprint (and eventually to paper)
• What are the moving pieces in the Javascript part ( @richford )?
• I want to add an AFQ-browser into my lab website. How do I do that?
• How do I cite the AFQ-browser project

[richford]

@anotherjoshsmith and I should write documentation for each js file.

[richford]

javascript documentation added in #226 and #228.

[arokem]

People shouldn't put these on their lab website, because it would break afqvault and binder.

[arokem]

OK - all of these are handled in #234, which I believe is now ready to go!

[richford]

Resolved by #252.