Documentation Pass

Added a quick start guide to the docs, component documentation to the options guide, some magic comments, and added CORS comments to the text track guide.
Not directly related to this PR, but as you mentioned yesterday, this is kinda jenky. I'm trying to think of reasons why we couldn't pull component settings up to the top level of options. e.g.

```
playerOptions = { "muteToggle": false };
```
The main issue would be if you had two of the same component type in the player and wanted them to behave differently. But we can leave the current way of setting these options as an alternative to be more specific.