Migrate documentation

[ect123]

Migrate existing documentation to appropriate pages:

• about.md (about the collection, maps, etc.)
• tutorial.md (how to use the application)
• README.md (project/technical documentation for anyone hoping to reuse the site)

[ect123]

Include technical prerequisites for developer documentation, and make the markdown template a downloadable file.

[nickmmurphy]

README.md is updated but needs review on technical documentation. The link for the markdown template needs to be tested once the update-readme branch is merged to develop.

[nickmmurphy]

README.md is updated but needs review on technical documentation. The link for the markdown template needs to be tested once the update-readme branch is merged to develop.

The link was broken and has been fixed.

[nickmmurphy]

Information has been added to the tutorial.md on the update-tutorial-page branch. After updating it, I wondered if the information about what the OIMOM is might be better suited to living on the home page. Additionally, the "how to" section might benefit from being on the same page as the mapbox, so that users can follow along with each step without needing to switch pages to read the directions. Any thoughts, @ect123?

[ect123]

As we discussed, let's see if we can migrate the tutorial content to an info "window" or "content box" that is visible to the user on each map view pages. The box should be toggle-able so that it takes up a minimal amount of space on the page, by using a button, icon, or some other visual cue to turn on or display. Once this is done, then we don't need the extra page.

[nickmmurphy]

README.md and tutorial content are both integrated, which leaves the "About" page on the OIMOM with information about the project and the library itself.