We'd like to develop some re-useable documentation here. We are primarily focused on creating a self-contained reference for the Duke workshop on August 27-28, 2013, but plan on updating this as a sustained user manual for future workshops and continuous use. Some principles:
- Self-contained for essential details, but not unnecessarily duplicative with other sources.
- Examples should easily work and not require guesswork for the users
- Avoid assuming unspecified dependencies; specific assumptions should be spelled out reasonably.
- Strive for high quality and style (no grammatical errors, typos, or expert idioms)