style guide

[shabbychef]

Having a general style guide in place before the code base grows might prevent headaches in the future. Such a style guide should include best practices on documenting the help for a function. (Perhaps this is a separate issue in its own right, since documentation should be usable in multiple contexts--at the repl, generated into a web page, etc.)

[JeffBezanson]

Style guide is a good idea.
Currently we're keeping function help in the reference section of the manual, and it is available in the repl via the help() function (we download and parse the markdown). Not fancy, but works.

[StefanKarpinski]

I still prefer two-space indentation.

[ducks]