In many older tutorials, we use things like var and .then() that we forbid in our actual codebase. It would be more readable if the docs used a more modern syntax, especially around Promises. Not only is await easier to read, but our use of .then() in docs may mislead a reader into thinking that they must do the same.

According to the HLS specification, we must sinalize that a given audio track is DVS by the addition of CHARACTERISTICS="public.accessibility.describes-video" tag. I wonder if we should implement an option at the Sequence level on mapped mode where I set "dvs": true or something and that propagates all the way to the HLS manifest. Thoughts on this one @erankor?

More information about this o

Apparently the parsing process has some kind of error, if a sprite is specified in the VTT file relative to the VTT file, then the player loads the sprite relative to the root of the site

In the case that is

While trying to learn how to use EVDI I discovered that evdi_get_event_ready is mentioned in the Quick Start, but not the detailed documentation. As I understand it, the detailed documentation is supposed to document all of libevdi.

Problem

We have a lot of public APIs that do not come with any sort of documentation 😭

Potential Solution

Add javadocs for all public APIs with example usages.

Impact

Improve the ease of use of the library.

Recently, we changed the setup tutorial. We should probably take new screenshots to reflect these changes.

Overview

As a user of the bootleg token, so I can try out the buying/selling process update the documentation so that it is clear how to use the BootegTokenApp contract and it's features.

Acceptance

• Bootleg website/SDK content updated with new content about the App, how to use it, where the code is on github
• Updated readme's in bootleg repo with mention of the App contract and how to u