Deploy gh-pages branch from travis

## [WiP] for task #34 

(this is #44 but merged into a local branch so that we can all push commits to it and we can test the results in this repository)

To safely deploy with couscus from a travis build we need to take this things into consideration:

- [x] Make sure the deployment is running only for master.
- [x] Make sure it is not a pull request.
- [ ] Make sure we deploy once per build. E.G. don't deploy for every PHP version tested :smile:
- [x] Decide what to use to deploy: [Private Key](http://stackoverflow.com/questions/23277391/pushing-to-github-from-travis-ci) or [Personal Access Token](http://stackoverflow.com/questions/18027115/committing-via-travis-ci-failing)  
    - More info on [Personal Access Token](https://medium.com/@nthgergo/publishing-gh-pages-with-travis-ci-53a8270e87db)
- [ ] Write documentation in `docs/travis.md`

Step by step to achieve the deploy:

Terminology:

- **PAT** = Personal Access Token

1. Install Travis on CLI `$gem install travis`
2. `$travis login` in the repo directory, this is needed to encrypt the **PAT**.
3. Generate a **PAT** from your GitHub account: Settings >> Applications >> Personal Access Token  
3.1 Giving it `public_repo` permission should be enough.
4. `$travis encrypt GH_TOKEN=PERSONALACCESSTOKENHERE --add`  
4.1 The `--add` flag will automatically write the encrypted string to your `.travis.yml` file.

Feel free to add commits and keep working on this together.
Should the command return `0` instead (here and below in the class)? Anything not `0` is interpreted as an error, so I'm afraid it might fail Travis build.