Documentation structure #101
Description
#83 (comment) raised the discussion of how to best document the use of virtualship, since I can imagine there will be information that is specific to the tool itself (e.g, "you need to get your credentials, define your space time region such that there is a bit of a buffer around your schedule, and then run the fetch command"), and then there is information that is more just course content.
How do you see these fitting together @ammedd ? Do you see virtualship being used outside of the context of the course content? (and, if so, is that only a long term goal?)
Perhaps it would be best to talk more on this after the course content has been made, and then we can see which parts are tool-specific information that would be best served as documentation?