Separate documentation for different users

[k8hertweck]

Data curators are the users who will spin up the app (and perhaps modify the browser), munge/load data, and share the resulting browser with collaborators.

Browser users will only need to launch the app.

We assume these users have different levels of computational expertise. Browser users may only require a subset of dependencies as well?

[k8hertweck]

This is a good place to mention the image I'm creating that shows the overall process of data generation -> data browsing, including what steps happen along the way (and what expertise is needed at each step). I'll add a draft here when it's available.

[ergonyc]

I think that currently non-curators are not supported... We should definitely make a roadmap for bringing "browsers" onboard. It will require:

• interactive data curation: "upload" files. "Choose" directories. "export" DATABASE, etc.
• automatic configuration tools

[k8hertweck]

Current documentation differentiates between "Curators" and "Viewers."

The Quickstart has extensive instructions for Curators, and it should be fairly straightforward to develop a short document walking Viewers through the process of unzipping a file and launching an app created by someone else.

The items mentioned above would be amazing enhancements for expanding the capacity of the browser itself.