Documentation update

Author: Mario Blazek

doc/ACTIONS.md

@@ -1,4 +1,5 @@
-# Actions
+Actions
+=======
 
 ### Available actions
 
@@ -8,23 +9,14 @@ This bundle has some already developed actions:
 
 Database action stores form data to database, to be specific, to `ezinfocollection` and `ezinfocollection_attribute` tables.
 
+For advanced configuration please refer to [configuration](CONFIGURATION.md) part.
+
 #### Email
 
 Email action sends email with form data to configured email address, that may be set in content type or configuration.
 For every content type different Twig template can be applied. Default template for emails must be specified.
 
-Per content type email template configuration example:
-
-```yaml
-netgen.default.information_collection.email.ng_feedback_form: 'AcmeBundle:email:ng_feedback_form.html.twig'
-netgen.default.information_collection.email.some_other_form: 'AcmeBundle:email:some_other_form.html.twig'
-```
-
-Default email template configuration example:
-
-```yaml
-netgen.default.information_collection.email.default: 'AcmeBundle:email:default.html.twig'
-```
+For advanced configuration please refer to [configuration](CONFIGURATION.md) part.
 
 ### Creating custom actions
 
@@ -74,9 +66,8 @@ netgen_information_collection:
                default:
                    - email
                    - database
-               content_type:
-                   my_content_type:
-                       - email
-                       - database
-                       - custom_action
+               my_content_type:
+                   - email
+                   - database
+                   - custom_action
 ```

doc/CHANGELOG.md

@@ -1,4 +1,6 @@
-# Change Log
+Changelog
+=========
+
 All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](http://keepachangelog.com/)

doc/CONFIGURATION.md

@@ -1 +1,52 @@
-# Configuration
+Configuration
+=============
+
+Some advanced use cases.
+
+## Specifiying which action to run per content type
+
+By default all actions set by *default* under *actions* tree will be executed for all content types.
+ 
+```yaml
+actions:
+    default:
+        - email
+        - database
+```
+
+To run only specific action for given content type, for example *my_content_type* and *email* add this to configuration:
+
+```yaml
+actions:
+    default:
+        - email
+        - database
+    my_content_type:
+        - email
+```
+
+Or to execute only *database* action for *my_content_type_2*:
+
+```yaml
+actions:
+    default:
+        - email
+        - database
+    my_content_type:
+        - email
+    my_content_type_2:
+        - database
+```
+
+## Specifiying which email templates to use per content type
+
+In case when want to split email templates per content type, rather than using default one all, add this to configuration:
+
+```yaml
+action_config:
+    email:
+        templates:
+            default: 'AcmeBundle:email:default.html.twig'
+            my_content_type: 'AcmeBundle:email:my_content_type.html.twig'
+            my_content_type2: 'AcmeBundle:email:my_content_type2.html.twig'
+```

doc/DOC.md

@@ -1,5 +1,5 @@
-NetgenInformationCollectionBundle
-=================================
+Documentation
+=============
 
 ## How it works
 

doc/FIELD_HANDLERS.md

@@ -1,4 +1,5 @@
-# Field handlers
+Field handlers
+==============
 
 ### Creating custom field handlers
 

doc/INSTALL.md

@@ -1,5 +1,5 @@
-NetgenInformationCollectionBundle installation instructions
-===========================================================
+Installation instructions
+=========================
 
 Requirements
 ------------
@@ -12,7 +12,7 @@ Installation steps
 
 ### Use Composer
 
-Run the following from your website root folder to install Netgen InformationCollection Bundle:
+Run the following from your website root folder to install NetgenInformationCollectionBundle:
 
 ```bash
 $ composer require netgen/information-collection-bundle