Merge pull request #17 from spryker-sdk/example-of-directories-structure

Updated README file with examples of directories structures

README.md

@@ -102,6 +102,32 @@ If you only need to add a new Spryk configuration you will start by adding an In
 
 When this is done run the Integration tests with `vendor/bin/codecept run Integration -g {YOUR TEST GROUP}` and see the test failing. You will get a message that the Spryk definition was not found by the given name, so add the definition file for you new Spryk. 
 
-You need to add your Spryk definition file into `vendor/spryker-sdk/spryk/config/spryk/spryks` when you added your new Spryk definition file re-run the tests. Now it dependends on the spryk type you choosed for your Spryk definition what comes next.
+You need to add your Spryk definition file into `config/spryk/spryks/` on project or core level:
 
-If you selected the template Spryk you will most likely see the error that the defined template file could not be found. In this case you need to add your template to `vendor/spryker-sdk/spryk/config/spryk/templates` when this is done re-run your tests. Now you should see a green test.
+```
+project OR package root directory
+│
+└─── config/
+│   └─── spryk/
+│   │    └─── spryks/
+│   │         │   ...
+│   │         │   spryk-name.yml
+│   │         │   ...
+│   └─── ...
+```
+
+If you selected the template Spryk, you will most likely see the error that the defined template file could not be found. In this case you need to add your template to `config/spryk/templates/` on project or core level:
+
+```
+project OR package root directory
+│
+└─── config/
+│   └─── spryk/
+│   │    └─── templates/
+│   │         │   ...
+│   │         │   template-name.twig
+│   │         │   ...
+│   └─── ...
+```
+
+When this is done re-run your tests. Now you should see a green test.