diff --git a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
index 38b6ead5..bf2dcc62 100644
--- a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
+++ b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
@@ -104,7 +104,45 @@ That was a targeted template: EiffelStudio will propose it whenever the user typ
=Sharing code templates=
+You can share your code templates using Github
+
+=Contributing Code Templates EiffelStudio=
+
+* Fork the project (https://github.com/EiffelSoftware/EiffelStudio), clone your fork, and configure the remotes:
+
+# Clone your fork of the repo into the current directory
+git clone https://github.com//
+# Navigate to the newly cloned directory
+cd
+# Assign the original repo to a remote called "upstream"
+git remote add upstream https://github.com//
+
+If you cloned a while ago, get the latest changes from upstream:
+
+
+git checkout
+git pull upstream
+
+
+# Create a new topic branch (off the main project development branch) to contain your new code template
+
+git checkout -b
+Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.
+
+Locally merge (or rebase) the upstream development branch into your topic branch:
+
+git pull [--rebase] upstream
+
+Push your topic branch up to your fork:
+
+git push origin
+
+# Open a Pull Request with a clear title and description
+
+
+# Code Template Review
+For your work to be integrated into the project, the maintainers will review your work and either request changes or merge it.