Clarify workflow on README.md

[MitchLillie]

Steps to reproduce:

0. Be mildly clueless
1. Visit https://github.com/hackoregon/getting-started

Current behavior:

• A list of links are displayed, organized into two groups—Installing Python and Jupyter Notebook and Installing Postgres/PostGIS.

Expected behavior:

• Ordinal steps, even if unnecessary, are presented as a guide.
• Logic branches (eg, Windows? Do this. Mac? Do this, or this for a more advanced install) further guide the user.
• Troubleshooting section clearly demarcates steps only necessary if a user experiences an issue.
• Explanatory information on the tools & libraries is presented (eg, what is Jupyter Notebook, and how will we be using it?).

[znmeb]

Thanks!! Once you get past the table of contents, most of the writeups are much clearer. Given that the source is Markdown, we could do something like GitBook or RStudio Bookdown to make a textbook from this. Or we could use the Python Read the Docs framework.

I can definitely do the GitBook or Bookdown editing ... I'm not a reStructured Text person so I'd have to foist this off on someone else if we go with Read the Docs. If you install the r-platform, rstudio-server and r-authoring options, the Bookdown editing / document production can be done in the virtual machine!

[scottslewis]

znmeb: I will take a shot at improving this during Thanksgiving week...if you are ok with that.

[znmeb]

Go for it - it needs some fresh eyes!!

[scottslewis]

Hi Mitch and Ed. I've taken a shot at organizing things in a more step-by-step manner and added some documentation for the virtual machine (Hack Oregon Base v2.ova) install. Please take a look starting
here https://github.com/hackoregon/getting-started (in Readme.md).