Restructure docs/doc-source

[drnikko]

problem: the structure of the repo is confusing, setting up local environments is time-consuming (and thus a barrier to participation).

details: This repo was initially built for developers to pull in programatically into their projects, and so we needed a way to have the "raw" text of the questions and answers and also a pleasant, human-readable website version for people who aren't comfortable/don't need to be in github. Thus, the docs vs docs-source current configuration.

what's next: I'd love to start a conversation about how to change this and figure out what the priorities are moving forward.

Thanks to @lee0c for revitalizing the issue about this in #74

[lee0c]

For the current layout, a simple directory naming change may make all the difference. Something like src/source and site/website/gh-pages (if it's hosted in github pages, idk) - indicates that one folder is unambiguously the source of the info, and the other is primarily files for the website.

I've seen there's some other issues proposing a machine-readable format like json, which would probably not play well with the source vs site structure I proposed right above - I'm not sure how inclusion of json would change either the stored files or the build process for the site. Would it replace some or all of the source material, or live alongside? If alongside, is it a separate top-level directory (Sphinx could probably ignore it in the build, so it could live in the current source directory - but that might be confusing?)