add documentation

[GochoMugo]

The documentation should lower the barrier to start contributing to the project. Topics include:

• [x] application architecture
• [x] collaboration
• [x] note on Code of Conduct
• [x] note on License, Contributing agreement
• [x] deployment information

[BransonGitomeh]

on deployment you can add an npm script to do a push to openshift automatically kinda like this logger

https://github.com/BransonGitomeh/Genesis/blob/master/package.json#L9

[GochoMugo]

Am actually having Travis CI deploy the application to OpenShift on commit on master branch. See in the configuration file: .travis.yml and Openshift deployment on Travis CI.

[BransonGitomeh]

deploy on commit :-| what happens when you commit incomplete stuff hah :-)

[GochoMugo]

We NEVER push to the master unless we are merging the develop branch, during a release.

[BransonGitomeh]

aaah i see, do you like the idea of feature branches?...

[GochoMugo]

We use a git branching model similar to this one.

[BransonGitomeh]

aah..i like PR's though...like work withing a pr in a branch for a feature, each major feature has a branch , but ill try to follow that

[GochoMugo]

Added in v0.2.0