write developer guide: setting up a dev environment

write a bunch of .md or .org files that explain to a novice developer how to set up a dev environment so they can be productive. commit them under www/doc/. This is basically Tutorial 9, but it probably belongs outside of the main end-user-facing web page. http://www.legalese.io/tutorials.html#t9

to earn the Legalese Tech Contributor badge, the following badges are required:

Basic Javascript. the object model. basic data structures. lambda expressions.
Some exposure to XML / HTML. tags, attributes, and CDATA and how they fit together in a tree.
Basic understanding of internet protocols, particularly HTTP.
Basic Git.
Basic Editing. In an editor such as Emacs, Vim, or Atom.
PlainText. familiarity with md or org formats. emacs users see http://orgmode.org/, others learn md.
Tutorial 7-Dan Champion. has run tutorial up to http://www.legalese.io/tutorials.html#t7

to develop Legalese's tech infrastructure, a contributor should:

set up their dev version of the google apps infrastructure, so they can see the effect of editing the .js files without having to push to the live production site.
set up their dev version of the XML templates archive, which the google apps reads over HTTP, so they can see the effect of editing the .xml files without having to push to the live production site.

The above are the two main areas that are under construction.

There is one less active area:

(if they're hacking the XML2PDF pathway) set up InDesign locally, so they can see the effect of editing the .jsx and .indt files without having to push to the live production site, which at the moment is a mac mini in a closet somewhere. The current reference version is InDesign CC 2014 but if you can't get your hands on that for whatever reason, it's OK to just use the latest.

Write a developer guide that explains to someone how to set up their dev environment. Assume they have no special privileges in github besides a normal user account. Contributions are expected to arrive in the form of pull requests. After the contributor earns the Legalese Tech Contributor badge, the contributor may earn the Legalese Developer badge, and win commit privileges into the main repository.

The guide should mention how the Available Templates page of the Demo Master can be forked for local variation.

this relates to issue #7.

legalese / legalese.github.io

write developer guide: setting up a dev environment #66