Fix documentation

The documentation needs to be fixed.

Currently, Sphinx throws lots of errors and warnings and the generated HTML is missing parts and even whole pages. It also looks like files are getting duplicated now (maybe due to changes in how Sphinx does things?): newly generated sources have .rst.txt as file extension, but files with the same contents already exist with a .txt extension. (These files are saved in the _sources dir of the generated docs.)

As far as I can tell, Sphinx is supposed to incorporate the docstrings of certain classes/methods on some pages, and that is currently failing, so I’m guessing these “includes” aren’t referenced correctly (anymore).

[keikoro]

@flothesof Oh, I knew how to do it alright. But the docs are broken.

And yeah, the idea of adding a CONTRIBUTING.md file to the repo in the future is floating around, and there’s also a Wiki (or the beginnings of a Wiki). Though I think we should fix the docs first before making people aware of how they could theoretically contribute.

[tburrows13]

The instructions at https://github.com/Zulko/moviepy#documentation are:

Running build_docs has additional dependencies that require installation.

$ (sudo) pip install moviepy[docs]

The documentation can be generated and viewed via:

$ python setup.py build_docs

These worked fine for me, and output the result in docs/build/html. Then all that is required is copying that into the gh-pages branch (this could definitely be streamlined further).