create base for readthedocs sphinx site

[clintonsteiner]

Generate with

sphinx-build -b html ./source ./build

or

make html

[clintonsteiner]

Linking https://github.com/akaihola/darker/issues/78

[akaihola]

In setup.cfg, we should probably add sphinx to either darker[release] extra dependencies, or to a new darker[docs] extra.

[clintonsteiner]

#766
Think this is probably a better approach, thoughts?

[akaihola]

#766 Think this is probably a better approach, thoughts?

#766 is indeed way simpler and adds minimal changes. It's a better approach as long as we choose to stick with a single page of documentation.

I'm trying to think of any benefits from full-fledged multi-page documentation with a more focused README. The change log and contribution guide could then of course be rendered as part of the documentation pages, and maybe more technical detail included as a separate page.

What do you think about the trade-offs between the two approaches?

[clintonsteiner]

#766 Think this is probably a better approach, thoughts?

#766 is indeed way simpler and adds minimal changes. It's a better approach as long as we choose to stick with a single page of documentation.

I'm trying to think of any benefits from full-fledged multi-page documentation with a more focused README. The change log and contribution guide could then of course be rendered as part of the documentation pages, and maybe more technical detail included as a separate page.

What do you think about the trade-offs between the two approaches?

I think choose the simple option until theres a reason to do the hard one