Feedback from going through Tutorial

[ebuchman]

Comments and hiccups from going through the tutorial:

• [ ] Why is email associated with a signature? Presumably it should be associated with a profile. Ie I'm likely to have one signature I use for every profile, but each profile will be for a different entity and use a different email (xxx@informal.systems, xxx@interchain.io, etc.)
• [ ] Clarify that params files need to be manually created, and provide some detail on how to do so (or required minimal background reading on dhall)
• [ ] contract.dhall example file is provided in the tutorial but apparently it's supposed to be generated by the tool. How does one generate it?

I basically got stuck here as I couldn't figure out how to generate the contract.dhall file and thus how to update it.

If I naively run themis-contract update contract.dhall I get:

$ themis-contract update contract.dhall 
3:08PM INF Loading contract: contract.dhall
3:08PM ERR Failed to load contract error="failed to convert Dhall file /Users/ethanbuchman/programming/goApps/src/gitlab.com/informalsystems/contractor-agreement/contract.dhall to JSON: exit status 1"

And so I wasn't able to get to part 3 of the tutorial.

We can probably simplify the tutorial by first focusing on the base case for using the tool locally (without reference to remote repos):

• Create a template
• Create params file
• Generate the contract.dhall (presumably this is automatic?)
• Compile
• Sign

Then we can go through doing similar things based on a template in a remote repo

[ebuchman]

• [x] pandoc-crossref requirement needs to be added to README

[ebuchman]

• [ ] Signature image is big, should be resizable (maybe a new issue ...)

[ebuchman]

• [ ] update the package.dhall URL in the contract.dhall