Expand the documentation (and maintain it as new features are added).

[audreytoskin]

Ideally, a graphical interface should be "self-documenting" however much that is possible; however, Ivy has some legit command line features, and the GUI will become less obvious as you add more features. I propose a three- or four-prong attack strategy:

• update the command line informational messages. The --help message is a little strangely formatted, and the purpose of the slashes isn't super clear. Adding a --version flag might be good too, now that you're tagging versions.
• Write a man manual page. Maybe a GNU Info page too?
• Keep up with documentation here in the README file.

Something like PanDoc might be helpful for mirroring the content between different file formats.

[lehitoskin]

I've added a manual page created by pandoc. There's content parity between -h and README.md and the manual page.