Add proper documentation for user-facing features

[rogermparent]

This PR has two main goals:

• Remove the current dummy docs which are an old copy of dvc.org's
• Use our current examples page as a basis for theme docs that this site will be dedicated to, fixing document features #17
• Copy over dvc.org contribution docs

If any glaring flaws are discovered in feature code and can be handled quickly, I'll consider fixing them and documenting so in this PR. Larger issues that could delay these docs will be noted and handled in follow-ups.

[yathomasi]

If any glaring flaws are discovered, they'll be fixed and documented in this PR unless it makes more sense to do otherwise.

I have been doing that https://gatsby-theme-iterative-example.herokuapp.com/doc/examples. We can continue documenting any feature we fix/add/update.

[rogermparent]

I see you have, and it's definitely a step in the right direction, but we probably want to elaborate more on the docs to the point where we give each feature its own page instead of having one mega-page for all features hidden among all the dummy docs. That work won't go to waste, though! it's a great starting point for where we want to go with this docs site.

The quote you have was also more directed toward the features themselves: if I discover a glaring flaw while writing documentation, that code may be fixed in this PR. It could also go the other way if the fix seems like too much to put in here- we can document the issue and follow up on it.

[yathomasi]

Thanks @rogermparent. Closing this as I don't see it's being updated any time soon.