Update docs for typescript->master merge & release

[jacobwindsor]

The docs in the Typescript branch are out of date. There is now this UI component and some other changes.

@ariutta what needs to be on the docs? I am happy to update them but it would be good to have a starting point as to what needs to be done so i can investigate the corresponding code

[jacobwindsor]

The 6.0.0-1 release is not working when installing via npm. I have fixed all of the issues in subsequent commits. I think it's best to just delete that release and make a new one.
Everything works fine now when using

"bridgedb": "git://github.com/bridgedb/bridgedbjs.git#c9c62df8487f49f1ad7a1c2614b6680d879331e7",

So a release on NPM should work

[ariutta]

Do you have an NPM account? I can add you to the bridgedb package.

[ariutta]

For the docs, I was originally using a tool that created docs from JSDoc comments. Now that we're using TS, we could look into using one of the documentation generators for TS, such as one of these:

https://www.npmjs.com/package/typedoc
https://www.npmjs.com/package/tsdoc

I'd like to keep the documentation in a separate branch (probably gh-pages). The source code branches like master and typescript should not put build artifacts like compiled JS and documentation under version control.

[ariutta]

On NPM, releases are pretty much immutable now. But we can always keep bumping the version. For deciding on version numbers, I'm trying to stick with semver: http://semver.org/