Add first version of the README template for Github

Why:

* The purpose of having a template is help setting up a README. Sometimes we don't know what to write, or how to structure it. It also helps in uniformizing our READMEs across projects. It probably won't fit every use case, but I believe it will fit most. It's not written in stone, so changes will always be welcome.

This change addresses the need by:

* Adding a template to use in all Github projects.

Author: gabrielpoca

github/README.md

@@ -24,3 +24,8 @@ Working on Issues/Pull Requests
 * Submit a Pull Request with the fix.
 * If your Pull Requests fixes one or more issues, link to them in the discussion.
 * Tag a person (or [team](https://github.com/orgs/subvisual/teams)) if you need their input specifically.
+
+Creating a repository
+-----------------------
+
+* If you are creating a Github repository, use the [templates](templates).

github/templates/README.md

@@ -0,0 +1,98 @@
+[trello]: https://trello.com/whatever
+[build-page]: https://semaphore.com/whatever
+[production]: https://link.to.production/
+
+PROJECT NAME
+============
+
+Put the build badges here.
+
+* [Trello][trello]
+* [Build Page][build-page]
+* [Production][production]
+* ...
+
+Short project description. You can use the client's pitch. No more than ten lines.
+
+**Table of Contents**
+
+* [Setup](#setup)
+* [Development](#development)
+* [Deployment](#deployment)
+* [More Sections](#more-sections)
+* [Contribution Guidelines](#contribution-guidelines)
+* [Resources](#resources)
+* [Contacts](#contacts)
+
+Setup
+-----
+
+A set of instructions to install the project. It can start with a list of dependencies, like databases, and finish with the instructions. For instance:
+
+First clone the repository to your file system:
+
+```
+git clone git@github.com:subvisual/guides.git
+```
+
+After, run the setup script:
+
+```
+bin/setup
+```
+
+To finish, open the file `.env` and replace the values accordingly.
+
+Development
+-----------
+
+A set of instructions to run the project in development. For instance:
+
+To start your development environment run:
+
+```
+bin/server
+```
+
+This will start the node application, Redis, and Gulp.
+ProjectName uses Gulp to watch and compile frontend assets.
+To build the assets only once, not watching for changes, run:
+
+```
+npm run build
+```
+
+Deployment
+----------
+
+Deploys can be manual or automatic. In both cases, write a short explanation about how it works: if the process is manual write the steps necessary to accomplish it; if the process is automatic, link to the page to consult the deployment status. Take the following as an example:
+
+To deploy the app run `bin/deploy`
+
+More Sections
+-------------
+
+This section is just a placeholder. You can replace it with any section or sections. Here you can write everything you feel the reader should know should about the project. This is the place to document other commands that are available to the user, or instructions on how to do something that's manual
+
+Contribution Guidelines
+-----------------------
+
+Contributions must follow [Subvisual's guides](https://github.com/subvisual/guides).
+
+Resources
+---------
+
+This section should list every online resource that is relevante to the project. For instance:
+
+* Link to spec file on Goole Drive
+* Link to Invision files.
+* ...
+
+About
+-----
+
+ProjectName is maintained by [Subvisual](http://subvisual.co).
+
+[![Subvisual](subvisual_logo_with_name.png)](http://subvisual.co)
+
+If you need to contact the maintainer use [this](https://trello.com/b/svB6ZSce/areas-of-responsability-dris) trello board, or reach out to <a href="mailto:contact@subvisual.co">Some One</a> if you don't have access.