[Docs] Testing environment

[yurividal]

Hi. I'd like to suggest that we build some sort of standard config package that contains all (or most) possible features, pre-configured.
The idea is that, with this, anyone contributing to code can test that their code isn't breaking any existing features of functionality.
I'm personally guilty of this myself. Some of my contributions have fixed one issue and introduced another one, that I'm not able to reproduce because I simply don't use the feature on my setup.

For example, this package should contain slides with and without animations, grow to fit, shrink to fit, media, lists, YouTube videos, style overwrites, lists, images, overlays, dual language readings, etc etc etc.
We could have shows to test each feature, and we could add comments as messages to each slide, explaining the expected behavior of that slide or show.

The point is, when contributing to code, anyone can use it to test all (or most) scenarios that any users might encounter.

This might be hard to put together, maybe should live in a separate repo, where we can sync the files to. But, once established, it should be very helpful.

What do you think?

[vassbo]

Not sure, it requires a lot of work, it would be good for the auto size at least.
I don't have the resources to maintain that myself, so if anyone want to do that feel free to.