update docs for creating templates

Author: jalogut

README.md

@@ -46,15 +46,15 @@ For that you cannot use the `.phar` binary, so you need to install the project:
 
 ### Contribute with new templates
 
-* If you want to contribute with new templates, just do the following:
+* If you want to contribute with new templates, just follow this manual:
 
-    0. Create a new template following the manual: [How to create templates](vendor/staempfli/universal-code-generator/docs/createTemplates.md)
+    0. [How to create templates](docs/createTemplates.md)
 
 ### Private Templates
 
 If current templates do not fill your needs, you can easily create your own templates. Just follow the manual:
 
-* [How to create private templates](vendor/staempfli/universal-code-generator/docs/privateTemplates.md)
+* [How to create private templates](docs/privateTemplates.md)
 
 ## Prerequisites
 

docs/createTemplates.md

@@ -0,0 +1,63 @@
+# How to create new templates
+
+In order to create new templates you just need to do the following.
+
+## Template files
+
+0. Create new folder with your `templateName` into the `templates` folder.
+0. Create you template files under your new template.
+0. Set your placeholders:
+    * Placeholders must have the following format `${param_name}` 
+    * Placeholders are possible on files content as well as on folder/file names.
+
+## Template documentation
+
+0. Create a new folder called `.no-copied-config` into you template
+0. Add there a description.txt file with a short description that clarifies what the template is for:
+	* This description will be show when running `./mg2-codegen.phar template:info <template>`  		 
+
+### OPTIONAL
+
+* If your template requires some manual steps after the code is generated, you can document this info in:
+	*  `.no-copied-config/after-generate-info.txt`
+	* This info will be displayed at the end of the code generation command. You can also use placeholders on this file.
+
+* If you want that your template executes other templates before, you can set dependencies in:
+	* `.no-copied-config/config.yml` 
+
+		```
+		dependencies:
+		  0: <template-name>
+		  1: <template-name>
+		```
+
+### Example
+
+You can check a template example here [Template Samples](../samples)
+
+## Important info
+
+### Built-in Properties
+
+Following properties are automatically set:
+
+* `vendorname` -> calculated from registration.php
+* `modulename` -> calculated from registration.php
+* `CommentsCompanyName` 
+* `commentsUserEmail` 
+* `commentsYear` 
+
+### Multicase properties
+
+* For all placehoders two versions with `Uppercase first` and `lowercase` are created. That means, that for every praceholder there will be 2 created:
+
+    * **v**endorname = **c**ompanyexample
+    * **V**endorname = **C**ompanyexample
+
+    * **m**odulename = **e**xamplemodule
+    * **M**odulename = **E**xamplemodule
+
+    * **c**ustomparam = **s**omevalue
+    * **C**ustomparam = **S**omevalue
+
+* Thanks to that, the user needs to enter only 1 value but 2 different placeholders can be used on the templates.

docs/privateTemplates.md

@@ -0,0 +1,9 @@
+# Create own Templates just for you
+
+Do the same as in the Create Templates documentation but place your template into `privateTemplates` folder.
+
+* [How to create templates](createTemplates.md)
+    
+## Priority
+
+Private templates have the highest priority. That means, that if you create a template with same name as an exiting one, your private will be used.